8 Commits

Author	SHA1	Message	Date
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
Harshavardhana	e3da59c923	fix possible crash in bucket bandwidth monitor (#11986)	2021-04-06 11:03:41 -07:00
Klaus Post	51dad1d130	Fix missing GetObjectNInfo Closure (#11243) ... Review for missing Close of returned value from `GetObjectNInfo`. This was often obscured by the stuff that auto-unlocks when reaching EOF.	2021-01-08 10:12:26 -08:00
Harshavardhana	187129a907	fix comment in bucket bandwidth package	2020-10-17 00:38:54 -07:00
Ritesh H Shukla	0b53e30ecb	Clean up monitor on delete bucket (#10698)	2020-10-16 17:59:31 -07:00
Ritesh H Shukla	8a16a1a1a9	fix: misc fixes for bandwidth reporting amd monitoring (#10683) ... * Set peer for fetch bandwidth * Fix the limit for bandwidth that is reported. * Reduce CPU burn from bandwidth management.	2020-10-16 09:07:50 -07:00
Ritesh H Shukla	8ceb2a93fd	fix: peer replication bandwidth monitoring in distributed setup (#10652)	2020-10-12 09:04:55 -07:00
Ritesh H Shukla	c2f16ee846	Add basic bandwidth monitoring for replication. (#10501) ... This change tracks bandwidth for a bucket and object - [x] Add Admin API - [x] Add Peer API - [x] Add BW throttling - [x] Admin APIs to set replication limit - [x] Admin APIs for fetch bandwidth	2020-10-09 20:36:00 -07:00