mirror of
https://github.com/minio/minio.git
synced 2024-12-25 22:55:54 -05:00
2f9e2147f5
PUT calls cannot afford to have large latency build-ups due to contentious usage.json, or worse letting them fail with some unexpected error, this can happen when this file is concurrently being updated via scanner or it is being healed during a disk replacement heal. However, these are fairly quick in theory, stressed clusters can quickly show visible latency this can add up leading to invalid errors returned during PUT. It is perhaps okay for us to relax this error return requirement instead, make sure that we log that we are proceeding to take in the requests while the quota is using an older value for the quota enforcement. These things will reconcile themselves eventually, via scanner making sure to overwrite the usage.json. Bonus: make sure that storage-rest-client sets ExpectTimeouts to be 'true', such that DiskInfo() call with contextTimeout does not prematurely disconnect the servers leading to a longer healthCheck, back-off routine. This can easily pile up while also causing active callers to disconnect, leading to quorum loss. DiskInfo is actively used in the PUT, Multipart call path for upgrading parity when disks are down, it in-turn shouldn't cause more disks to go down. |
||
|---|---|---|
| .. | ||
| amztime | ||
| arn | ||
| auth | ||
| bpool | ||
| bucket | ||
| color | ||
| config | ||
| crypto | ||
| deadlineconn | ||
| disk | ||
| dsync | ||
| etag | ||
| event | ||
| fips | ||
| handlers | ||
| hash | ||
| http | ||
| init | ||
| ioutil | ||
| jwt | ||
| kms | ||
| lock | ||
| logger | ||
| lsync | ||
| mcontext | ||
| mountinfo | ||
| once | ||
| pubsub | ||
| rest | ||
| s3select | ||
| store | ||