Shutdown Cluster When Disk Space Approaches Max
Nobody has claimed this yet.
- Dominant language
- Erlang
- Stars
- 303
- Forks
- 211
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 5
Description
As a customer, I do not want my system to corrupt redis databases and refuse to come up after a DRBD or other disk full situation. I would like the system to notice the disk full situation, warn, and shutdown cleanly. This way, I can clean up and start back up without further incident.
https://github.com/chef/opscode-omnibus/commit/e2f3e59b91f8e6b9ba8a7b61faade8332e49c688
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked opscode-omnibus commit and the disk-full incident described in the issue. Trace where disk-space conditions could be detected and where a warning and clean shutdown would be coordinated; done means the system avoids corruption and can be restarted after cleanup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang, redis
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100