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.		2020-07-29 23:15:34 -07:00
..
.gitignore	Support MinIO to be deployed on more than 32 nodes (#8492)	2019-11-13 12:17:45 -08:00
drwmutex_test.go	preserve context per request for local locks (#9828)	2020-06-14 07:43:10 -07:00
drwmutex.go	fix: Pass context all the way down to the network call in lockers (#10161)	2020-07-29 23:15:34 -07:00
dsync_test.go	preserve context per request for local locks (#9828)	2020-06-14 07:43:10 -07:00
dsync-server_test.go	fix: Speed up multi-object delete by taking bulk locks (#8974)	2020-02-21 11:29:57 +05:30
dsync.go	Implement bucket expansion (#8509)	2019-11-19 17:42:27 -08:00
rpc-client-impl_test.go	fix: Pass context all the way down to the network call in lockers (#10161)	2020-07-29 23:15:34 -07:00
rpc-client-interface.go	fix: Pass context all the way down to the network call in lockers (#10161)	2020-07-29 23:15:34 -07:00