Harshavardhana c608c0688a fix: properly close leaking bandwidth monitor channel (#11967) ...

This PR fixes

- close leaking bandwidth report channel leakage
- remove the closer requirement for bandwidth monitor
  instead if Read() fails remember the error and return
  error for all subsequent reads.
- use locking for usage-cache.bin updates, with inline
  data we cannot afford to have concurrent writes to
  usage-cache.bin corrupting xl.meta

2021-04-06 12:40:42 -07:00

..

measurement.go

Add basic bandwidth monitoring for replication. (#10501)

2020-10-09 20:36:00 -07:00

monitor_test.go

fix: misc fixes for bandwidth reporting amd monitoring (#10683)

2020-10-16 09:07:50 -07:00

monitor.go

fix possible crash in bucket bandwidth monitor (#11986)

2021-04-06 11:03:41 -07:00

reader.go

fix: properly close leaking bandwidth monitor channel (#11967)

2021-04-06 12:40:42 -07:00

throttle.go

fix: misc fixes for bandwidth reporting amd monitoring (#10683)

2020-10-16 09:07:50 -07:00