Skip to content

rabbit_node_monitor: use a leader query for cluster members on node_added event (backport #11664) #11835

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

Merged
merged 3 commits into from
Jul 25, 2024

Conversation

mergify[bot]
Copy link

@mergify mergify bot commented Jul 25, 2024

If the membership hasn't been updated locally yet, the event is never generated


This is an automatic backport of pull request #11664 done by [Mergify](https://mergify.com).

…dded event

If the membership hasn't been updated locally yet, the event is never generated

(cherry picked from commit 19a71d8)
They must be sent during reset and when leaving the cluster for
any metadata store

(cherry picked from commit db03d8c)
This function is called directly from CLI commands, skipping the `rabbit_db_cluster` layer

(cherry picked from commit e856a6c)
@mergify mergify bot added the bazel label Jul 25, 2024
@michaelklishin michaelklishin merged commit 94942f6 into v4.0.x Jul 25, 2024
191 checks passed
@michaelklishin michaelklishin deleted the mergify/bp/v4.0.x/pr-11664 branch July 25, 2024 20:58
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.

2 participants