Harshavardhana 736e58dd68

fix: handle concurrent lockers with multiple optimizations (#10640) ...

- select lockers which are non-local and online to have
  affinity towards remote servers for lock contention

- optimize lock retry interval to avoid sending too many
  messages during lock contention, reduces average CPU
  usage as well

- if bucket is not set, when deleteObject fails make sure
  setPutObjHeaders() honors lifecycle only if bucket name
  is set.

- fix top locks to list out always the oldest lockers always,
  avoid getting bogged down into map's unordered nature.

2020-10-08 12:32:32 -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

allow lock tolerance to match storage-class drive tolerance (#10270)

2020-08-14 18:17:14 -07:00

drwmutex.go

fix: handle concurrent lockers with multiple optimizations (#10640)

2020-10-08 12:32:32 -07:00

dsync_test.go

fix: add lock ownership to expire locks (#10571)

2020-09-25 19:21:52 -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

rpc-client-impl_test.go

fix: handle concurrent lockers with multiple optimizations (#10640)

2020-10-08 12:32:32 -07:00

rpc-client-interface.go

fix: handle concurrent lockers with multiple optimizations (#10640)

2020-10-08 12:32:32 -07:00