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

raft: panic: applied(25) is out of range [prevApplied(10), committed(10)] #1878

Closed
tamird opened this issue Jul 31, 2015 · 5 comments
Closed
Assignees
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered).

Comments

@tamird
Copy link
Contributor

tamird commented Jul 31, 2015

Happened on my multicpu branch.

https://circleci.com/gh/cockroachdb/cockroach/5249

https://circle-artifacts.com/gh/cockroachdb/cockroach/5249/artifacts/0/tmp/circle-artifacts.6Xbc003/test.log

TestRaftRemoveRace specifically triggers this.

@tamird tamird added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered). multi-cpu labels Jul 31, 2015
@bdarnell
Copy link
Contributor

Looks like a race between GC and other raft operations, as discussed in #768 and #1865.

@tbg
Copy link
Member

tbg commented Sep 15, 2015

one more for the inclined: https://circleci.com/gh/tschottdorf/cockroach/1347

@bdarnell
Copy link
Contributor

I've reviewed all the linked logs and they all appear to be the same root cause, #768, which has been fixed by the combination of #2798 and #2823. Please open new issues if anything like this turns up again.

@tamird
Copy link
Contributor Author

tamird commented Oct 14, 2015

After rebasing #1839, I still see a failure in TestRaftRemoveRace:

panic: [group 1] applied(54) is out of range [prevApplied(0), committed(0)]

https://circleci.com/gh/cockroachdb/cockroach/8440
https://circle-artifacts.com/gh/cockroachdb/cockroach/8440/artifacts/0/tmp/circle-artifacts.HHAR97f/test.log

@tamird tamird reopened this Oct 14, 2015
@bdarnell
Copy link
Contributor

Let's make that a new issue then - even though the message is similar, the underlying cause looks different and it's not helpful to continue in this thread. Also, all the others in this thread had non-zero values for prevApplied and committed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. C-test-failure Broken test (automatically or manually discovered).
Projects
None yet
Development

No branches or pull requests

3 participants