5 Commits (1d1c4430b2cf2cb3c8328815bc2e1fd07e526fc7)

Author	SHA1	Message	Date
Harshavardhana	fe157166ca	fix: Pass context all the way down to the network call in lockers (#10161) ... Context timeout might race on each other when timeouts are lower i.e when two lock attempts happened very quickly on the same resource and the servers were yet trying to establish quorum. This situation can lead to locks held which wouldn't be unlocked and subsequent lock attempts would fail. This would require a complete server restart. A potential of this issue happening is when server is booting up and we are trying to hold a 'transaction.lock' in quick bursts of timeout.	4 years ago
Harshavardhana	ab7d3cd508	fix: Speed up multi-object delete by taking bulk locks (#8974) ... Change distributed locking to allow taking bulk locks across objects, reduces usually 1000 calls to 1. Also allows for situations where multiple clients sends delete requests to objects with following names ``` {1,2,3,4,5} ``` ``` {5,4,3,2,1} ``` will block and ensure that we do not fail the request on each other.	5 years ago
Harshavardhana	720442b1a2	Add lock expiry handler to expire state locks (#8562)	5 years ago
Harshavardhana	347b29d059	Implement bucket expansion (#8509)	5 years ago
Harshavardhana	e9b2bf00ad	Support MinIO to be deployed on more than 32 nodes (#8492) ... This PR implements locking from a global entity into a more localized set level entity, allowing for locks to be held only on the resources which are writing to a collection of disks rather than a global level. In this process this PR also removes the top-level limit of 32 nodes to an unlimited number of nodes. This is a precursor change before bring in bucket expansion.	5 years ago