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

Develop 3.0 lastgaspring #1729

Merged
merged 5 commits into from
Nov 18, 2019
Merged

Develop 3.0 lastgaspring #1729

merged 5 commits into from
Nov 18, 2019

Conversation

martinsumner
Copy link
Contributor

See basho/riak_core#945

This depends on this riak_core PR.

Last gasp monitoring added in all 3 places where ensemble tries to react to ring changes. Also blocks vnodes starting on a lastgasp ring.

Otherwise a wave of crashing vnode starts can generate log noise during shutdown
But this appears to do so in a safer way
The tick on the backend is very aggressive.  So wait 20 ticks of a stable ring before reacting.  It would be preferable if other processes react to significant ring changes because of basho/riak_ensemble#129.

Perhaps this shouldn't do anything at all?
@martinsumner
Copy link
Contributor Author

@ThomasArts - this makes use of the lastgasp on the ring to avoid some of the log noise issues. Also has the necessary additional changes to stop riak_ensemble from firing off the last gasp ring.

Copy link
Contributor

@ThomasArts ThomasArts left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only after 20th tick the old logic kicks in

@martinsumner martinsumner merged commit 9bda045 into develop-3.0 Nov 18, 2019
@martinsumner martinsumner deleted the develop-3.0-lastgaspring branch November 18, 2019 11:21
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.

2 participants