-
Notifications
You must be signed in to change notification settings - Fork 4k
Shovels: fix shovel status and deletion of failed shovels #14637
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
Conversation
These shovels are stuck in a restart loop and need to be listed on shovel status, which also allows for its deletion
|
One of two scenarios seems to be resolved. Scenario 1 (seems solved): and delete them shortly after This was not deterministic but usually afterwards I'd have 1 shovel listed on Scenario 2 (still failing): Such a shovel is failing with: Now try to delete it: |
|
one more scenario I now tried: a happily running shovel can be deleted from any node (rabbitmqctl |
|
Just FTR, distributed shovels in Tanzu RabbitMQ should deal with that scenario well @mkuratczyk :) |
f8d7977 to
52b46c8
Compare
| %% terminated | ||
| ({Name, Type, {terminated, Reason}, Metrics, Timestamp}) -> | ||
| {Name, Type, {terminated, Reason}, Metrics, Timestamp}; | ||
| {Name, Type, {terminated, [{node, Node}], Reason}, Metrics, Timestamp}; |
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.
@michaelklishin Is this a breaking change? It seems just delete/restart CLI commands use cluster_status_with_nodes
Fixes deletion and restart
52b46c8 to
13201b2
Compare
e71db0b to
c9697a6
Compare
Shovels: fix shovel status and deletion of failed shovels (backport #14637)
These shovels are stuck in a restart loop and need to be listed on shovel status, which also allows for its deletion
See #14623