Skip to content

'rabbitmq-upgrade revive' command returns error #12013

Closed Answered by michaelklishin
alphamonkey79 asked this question in Other
Discussion options

You must be logged in to vote

I have pushed some Upgrades guide updates to make it clear that revive is not necessary in most cases, and its only purpose is to undo (some) effects of drain rabbitmq/rabbitmq-website@bb21df7.

@kjnilsson has identified an unintentional mistake in what queues do those command attempt to operate on, which can produce this and other unnecessary exceptions. Even though #12014 will handle this and most (if not all) other errors our Raft library can return, a separate fix for that is coming in 3.13.7.

Together with an easy to adopt workaround (a node must be restarted one way or another), this hopefully can be considered addressed.

Replies: 6 comments 4 replies

Comment options

You must be logged in to vote
1 reply
@michaelklishin
Comment options

Comment options

You must be logged in to vote
1 reply
@michaelklishin
Comment options

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
2 replies
@alphamonkey79
Comment options

@michaelklishin
Comment options

Comment options

You must be logged in to vote
0 replies
Answer selected by michaelklishin
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants
Converted from issue

This discussion was converted from issue #12013 on August 15, 2024 13:49.