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
ceph: update cluster storage utilization alert threshold and timing #4286
Conversation
There were the following issues with this Pull Request
You may need to change the commit messages to comply with the repository contributing guidelines. 🤖 This comment was generated by commitlint[bot]. Please report issues here. Happy coding! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Look at the bot for the commit
ec2675d
to
f1cc90e
Compare
There were the following issues with this Pull Request
You may need to change the commit messages to comply with the repository contributing guidelines. 🤖 This comment was generated by commitlint[bot]. Please report issues here. Happy coding! |
@anmolsachan The bot requires a prefix on the commit message, such as: |
This PR mainly takes a proactive approach to alert the user to take action when the cluster utilizartion is getting close to the maximum capacity. Since ceph stops I/O at 95% utilization, the user should be warned before it. Signed-off-by: Anmol Sachan <anmol13694@gmail.com>
f1cc90e
to
09af832
Compare
Thanks, @leseb @travisn. It was my first PR on this repo, did not know :) |
ceph: update cluster storage utilization alert threshold and timing (bp #4286)
Signed-off-by: Anmol Sachan anmol13694@gmail.com
Description of your changes:
This PR updates the Cluster storage utilization alert threshold and timing. This is an enhancement based on some experiments and observations.
This mainly takes a proactive approach to alert the user to take action when the cluster is getting close to the maximum capacity. Since ceph stops I/O at 95% utilization, the user should be warned before it.
Which issue is resolved by this Pull Request:
Checklist:
make codegen
) has been run to update object specifications, if necessary.[skip ci]