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

Make ensure_monitors more defensive in SAC coordinator #5897

Merged

Conversation

acogoluegnes
Copy link
Contributor

Do not assume the connection PID of a consumer is still known from the state on state cleaning when unregistering a consumer.

Fixes #5889

Do not assume the connection PID of a consumer is still
known from the state on state cleaning when unregistering
a consumer.

Fixes #5889
@acogoluegnes acogoluegnes marked this pull request as ready for review September 30, 2022 11:53
@michaelklishin michaelklishin merged commit e0a7cee into main Sep 30, 2022
@michaelklishin michaelklishin deleted the rabbitmq-server-5889-sac-coordinator-crash-in-monitors branch September 30, 2022 13:55
michaelklishin added a commit that referenced this pull request Sep 30, 2022
Make ensure_monitors more defensive in SAC coordinator (backport #5897)
@michaelklishin michaelklishin removed this from the 3.11.1 milestone Oct 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Stream 'crash' when using Single Active Consumer and restarting stream writer node
3 participants