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.

Sign up for GitHub

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

Jump to bottom

pg_local:member_died/1 should be more resilient #1699

Closed
michaelklishin opened this issue Sep 14, 2018 · 0 comments
Closed

pg_local:member_died/1 should be more resilient #1699

michaelklishin opened this issue Sep 14, 2018 · 0 comments
Assignees
@michaelklishin
Labels
bug effort-low
Milestone
3.7.8

Comments

@michaelklishin
Copy link
Member

See this rabbitmq-users thead.

If due to any reason a bookkeeping table behind pg_local groups doesn't have a record, pg_local:member_died/1 should be more resilient (a no-op) or use the pid information from the DOWN event that triggered it. Further cascading failures due to a badmatch won't be productive in any way.
@michaelklishin michaelklishin added this to the 3.7.8 milestone Sep 14, 2018
@michaelklishin michaelklishin self-assigned this Sep 14, 2018
michaelklishin added a commit that referenced this issue Sep 15, 2018
@michaelklishin
Make pg_local:member_died/2 more resilient
dc89457 
See #1699 for background.

[#160530707]
@michaelklishin michaelklishin mentioned this issue Sep 15, 2018
Merged
11 tasks
michaelklishin added a commit that referenced this issue Sep 17, 2018
@michaelklishin
Make pg_local:member_died/2 more resilient
2288f54 
See #1699 for background.

[#160530707]

(cherry picked from commit dc89457)
@michaelklishin michaelklishin mentioned this issue Nov 20, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelklishin michaelklishin

Labels
bug effort-low
Projects
None yet
Milestone
3.7.8
Development

No branches or pull requests
1 participant
@michaelklishin