Immutable solution version
Minio randomly ignores and not answer on http requests. (error 499 very often)
Complete solution
MinIO returning lots of 499s and ignoring HTTP requests isn't always a MinIO bug: in this case the maintainer traced xl.meta reads taking milliseconds (over 106 seconds to list 10k entries) when os.Open should take microseconds, meaning the drives were too slow and clients timed out. If you see random 499s after a version bump, check your drive latency from a minio trace before blaming the release; slow disks need better IOPs, not a config tweak.
MinIO - ## NOTE
When i am looking at minio trace, i see a lot of 499 errors.
The fix
MinIO returning lots of 499s and ignoring HTTP requests isn't always a MinIO bug: in this case the maintainer traced xl.meta reads taking milliseconds (over 106 seconds to list 10k entries) when os.Open should take microseconds, meaning the drives were too slow and clients timed out. If you see random 499s after a version bump, check your drive latency from a minio trace before blaming the release; slow disks need better IOPs, not a config tweak.
Thread: gh:minio/minio#17431
Evidence
In gh:minio/minio#17431 (https://github.com/minio/minio/issues/17431), the issue reported: ## NOTE
When i am looking at minio trace, i see a lot of 499 errors. [!--- Provide a general summary of the issue in the Title above --]
Expected Behavior
Previously we used version RELEASE.2022-06-03T01-40-53Z and everything was ok. [!--- If you're describing a bug, tell us what should happen --] [!--- If you're suggesting a change/improvement, tell us how it should work --]
Current Behavior
Now we are using version RELEASE.2023-06-09T07-32-12Z We are using minio as s3 backend for restic. and because of bug in restic it stucks periodically -... The verified answer: MinIO returning lots of 499s and ignoring HTTP requests isn't always a MinIO bug: in this case the maintainer traced xl.meta reads taking milliseconds (over 106 seconds to list 10k entries) when os.Open should take microseconds, meaning the drives were too slow and clients timed out. If you see random 499s after a version bump, check your drive latency from a minio trace before blaming the release; slow disks need better IOPs, not a config tweak.
By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_T3HtnXbQiiNCOYosUHydFw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Minio randomly ignores and not answer on http requests. (error 499 very often) <span>— Vectle</span></a>