Skip to content

Conversation

@dumbbell
Copy link
Collaborator

Why

That timer was started during boot and continued regardless if rabbit was running or stopped.

This caused the reconsiliation to crash if the rabbit app was stopped before the it ended because it tried to access the database even though it was stopped or even reset.

How

We just check if rabbit is running before running one reconciliation and scheduling a new one.

[Why]
That timer was started during boot and continued regardless if `rabbit`
was running or stopped.

This caused the reconsiliation to crash if the `rabbit` app was stopped
before the it ended because it tried to access the database even though
it was stopped or even reset.

[How]
We just check if `rabbit` is running before running one reconciliation
and scheduling a new one.
@dumbbell dumbbell self-assigned this Nov 25, 2024
[How]
The function now accepts that the node to reset is already out of the
cluster. This avoids a mismatch exception for a situation that is ok.
@dumbbell dumbbell marked this pull request as ready for review November 25, 2024 12:40
@dumbbell dumbbell merged commit ad2354b into main Nov 25, 2024
273 checks passed
@dumbbell dumbbell deleted the stop-vhos-reconciliation-if-rabbit-is-stopped branch November 25, 2024 12:40
dumbbell added a commit that referenced this pull request Nov 25, 2024
rabbit_vhosts: Don't reconcile vhosts if `rabbit` is stopped (backport #12799)
@michaelklishin
Copy link
Collaborator

Good catch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants