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

RabbitMQ: explain how to properly avoid an OrderedReady-induced deployment deadlock (take 1) #25873

Closed
wants to merge 4 commits into from

Conversation

michaelklishin
Copy link
Contributor

See #25698 and #16081 (comment).

For now, we can at least recommend the right thing to do.

Explain the problem and two widely used solutions
instead of recommending force booting nodes.

Signed-off-by: Michael Klishin <[email protected]>
@michaelklishin
Copy link
Contributor Author

I will take care of the Markdown linter failures.

@michaelklishin
Copy link
Contributor Author

michaelklishin commented May 14, 2024

My latest (force-pushed) commit does included a Signed-off-By, I don't know what else the DCO workflow expects to be done.

@michaelklishin
Copy link
Contributor Author

michaelklishin commented May 14, 2024

Moved to #25916.

@michaelklishin michaelklishin changed the title RabbitMQ: explain how to properly avoid a deployment deadlock RabbitMQ: explain how to properly avoid an OrderedReady-induced deployment deadlock May 14, 2024
@michaelklishin michaelklishin changed the title RabbitMQ: explain how to properly avoid an OrderedReady-induced deployment deadlock RabbitMQ: explain how to properly avoid an OrderedReady-induced deployment deadlock (take 1) May 14, 2024
michaelklishin added a commit to michaelklishin/charts-1 that referenced this pull request May 15, 2024
Signed-off-by: Michael Klishin <[email protected]>
Signed-off-by: Michael Klishin <[email protected]>
Signed-off-by: Michael Klishin <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants