-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
RFE: options for OSD restart gate #13811
Comments
Ok, this would be even a more strict option for upgrades, such as |
Exactly. This wasn't even an upgrade, it was a K8s-induced rolling restart. Since Alternately I'd love to even be able to introduce a configurable extra delay between OSD restarts, if that would be simpler. I.e., "sleep for 300 seconds after you get |
I think this feature requires check cluster if the PGs status is clean before upgrade any osds.
I'd like to take the issue😄 |
/assign |
Thanks for taking this issue! Let us know if you have any questions! |
Thanks for the feature! It occurs to me that I might have asked for a healthy mon quorum too but I think that's a lower risk. |
My understanding is that the operator gates OSD restarts via
ceph osd ok-to-stop
.I would like the option to change or augment this condition so that the operator will not proceed to restart the next OSD unless all PGs are
active+clean.*
We recently adjusted our K8s
requests
andlimits
settings and experienced a subset of inactive PGs that impacted clients on an EC HDD pool. My confidence inok-to-stop
has always been limited, but I don't have a smoking gun.Is this a bug report or feature request?
What should the feature do:
What is use case behind this feature:
Environment:
The text was updated successfully, but these errors were encountered: