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

Jump to bottom

Moving consensus FSM back to epoch start if there's unexpected system error #130

Closed
zjshen14 opened this issue Oct 1, 2018 · 0 comments
Closed

Moving consensus FSM back to epoch start if there's unexpected system error #130

zjshen14 opened this issue Oct 1, 2018 · 0 comments
Assignees
@FishMeat
Labels
enhancement New feature or request

Comments

@zjshen14
Copy link
Contributor

zjshen14 commented Oct 1, 2018

Currently, when any system error happens in consensus FSM, we will return an sInvalid state, and the fsm will stay at the current state. This makes the consensus be at the risk of being stuck unexpectedly. A better way is to move fsm back to epoch_start, which consensus could from restart from a fresh state.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@FishMeat FishMeat

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@FishMeat @zjshen14