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

recovery is impossible if more than f nodes fail at once #12

Open
evanmcc opened this issue Jun 14, 2017 · 1 comment
Open

recovery is impossible if more than f nodes fail at once #12

evanmcc opened this issue Jun 14, 2017 · 1 comment

Comments

@evanmcc
Copy link
Owner

evanmcc commented Jun 14, 2017

This is a protocol problem, at least when we're running in diskless mode (which will be the default, I imagine). In the end, this will likely require FSMs that require this sort of durability to implement from-disk recovery on their own, but we should provide tools to make this easier or a simple default implementation.

@evanmcc
Copy link
Owner Author

evanmcc commented Mar 31, 2018

ideas:

  • admin state dump, corresponding enhancement of the start command to take an initial state, so an admin can grab the state of the last nodes, declare it canonical and inject it into a new quorum.
  • allow behaviors to declare themselves as having persistent state, which should allow recovery from crashes if not node loss.

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

No branches or pull requests

1 participant