Harshavardhana 88c1bb0720 fix: improper ticker usage in goroutines (#11468) ... - lock maintenance loop was incorrectly sleeping as well as using ticker badly, leading to extra expiration routines getting triggered that could flood the network. - multipart upload cleanup should be based on timer instead of ticker, to ensure that long running jobs don't get triggered twice. - make sure to get right lockers for object name		2021-02-05 19:23:48 -08:00
..
.gitignore	Support MinIO to be deployed on more than 32 nodes (#8492)	2019-11-13 12:17:45 -08:00
drwmutex.go	fix: improper ticker usage in goroutines (#11468)	2021-02-05 19:23:48 -08:00
drwmutex_test.go	allow lock tolerance to match storage-class drive tolerance (#10270)	2020-08-14 18:17:14 -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	fix: add lock ownership to expire locks (#10571)	2020-09-25 19:21:52 -07:00
dsync_test.go	fix: add lock ownership to expire locks (#10571)	2020-09-25 19:21:52 -07:00
rpc-client-impl_test.go	fix: expire locks only on participating lockers (#11335)	2021-01-25 10:01:27 -08:00
rpc-client-interface.go	fix: expire locks only on participating lockers (#11335)	2021-01-25 10:01:27 -08:00