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

Node restart failure due to appliedIndex issue #36

Open
kingster opened this issue May 20, 2022 · 0 comments · May be fixed by #37
Open

Node restart failure due to appliedIndex issue #36

kingster opened this issue May 20, 2022 · 0 comments · May be fixed by #37
Labels
bug Something isn't working

Comments

@kingster
Copy link
Member

Node restart fails

2022-05-20 17:02:00.010255 W | snap: skipped unexpected non snapshot file 0000000000293406.snap.db
2022-05-20 17:02:00.010265 W | snap: skipped unexpected non snapshot file 0000000000295b18.snap.db
2022-05-20 17:02:00.010319 I | [Node 9ce42e481f88a68d] loading WAL at term 866 and index 2710344
raft2022/05/20 17:02:00 applied(2720223) is out of range [prevApplied(2710344), committed(2720222)]
panic: applied(2720223) is out of range [prevApplied(2710344), committed(2720222)]

This looks like post compaction the updated appliedIndex is not saved to the underlying data-store.
@kingster kingster added the bug Something isn't working label May 20, 2022
@kingster kingster linked a pull request Jun 3, 2022 that will close this issue
Fix panic due to appliedEntry checkpoint #37
Open
@kingster kingster linked a pull request Jun 29, 2022 that will close this issue
Open
@kingster kingster mentioned this issue Jul 7, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix panic due to appliedEntry checkpoint flipkart-incubator/nexus
1 participant
@kingster