Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add information about writes on nearly full disks #1335

Open
djwfyi opened this issue Oct 3, 2024 · 0 comments
Open

Add information about writes on nearly full disks #1335

djwfyi opened this issue Oct 3, 2024 · 0 comments
Assignees

Comments

@djwfyi
Copy link
Collaborator

djwfyi commented Oct 3, 2024

MinIO Object Store can run into limitations when disk usage approaches nearly full usage.

Add information to /operations/install-deploy-manage/expand-minio-deployment.html#capacity-based-planning and/or on the deployment pages that drives >90% full are at risk of critical performance issues and require

  • cleaning up old data
  • adding a pool

Additional info about writes on highly used disks/pools:

  • At >85% usage, writes are sent to pools with <85% usage when available
  • At >99% usage, writes can no longer happen, though overwrites can happen

Note that MinIO requires more than the space of actual objects to be able to write bucket metadata, pool.bin info, and many other processes. MinIO requires that drives remain writable. Administrators should begin planning expansion when pool usage reaches 80% and have the new pools in place by the time the pool reaches 95%.

Verify the percentage assumptions above with engineers.

This information could also go on:

  • operations/concepts/thresholds.html
  • operations/checklists/hardware.html
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants