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

When member was restarted previous incarnation can be marked as failed faster #132

Closed
antonkharenko opened this issue Nov 18, 2015 · 0 comments · Fixed by #209
Closed

When member was restarted previous incarnation can be marked as failed faster #132

antonkharenko opened this issue Nov 18, 2015 · 0 comments · Fixed by #209

Comments

@antonkharenko
Copy link
Member

Currently when you restart the node it will try to wait for configured timeout and ping previous incarnation during this time. But since on the same address already running member with another memberId it actually can be deducted that previous member will never return and can be cleaned out of membership table without waiting for timeouts.
@ronenhamias ronenhamias transferred this issue from scalecube/scalecube-services Dec 22, 2018
@artem-v artem-v mentioned this issue Jun 2, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

issue#132 / previous incarnation can be marked as failed faster scalecube/scalecube-cluster
1 participant
@antonkharenko