-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
storage: TestStoreRangeDownReplicate timeout due to stuck Raft command #9673
Comments
Reproduced this (or something similar) via
|
Seems likely, though the more interesting goroutine would be stuck in |
This may also be relevant for/connected to #9624 |
Here's
|
I can take this one. If you're interested, let's pair up (but ok if you just wanna do something else). |
It's a party in the TestStoreRangeDownReplicate: --- FAIL: TestStoreRangeDownReplicate (0.81s) |
How about this one:
|
Also expected (as far as I can tell, though I'm not sure why in this test). I'll send a PR. |
I obviously never sent that PR. My suspicion was that we're doing concurrent splits by accident, in which case it's perfectly reasonable that some of them would fail. I've got to clear out my queue now, so maybe @jordanlewis can pull this thread further when he gets back. |
seen in #9672: https://teamcity.cockroachdb.com/viewLog.html?buildId=25993&buildTypeId=Cockroach_UnitTests
It appears that a Raft command made it to a previously unreplicated Replica and is stuck on Raft. Ideally this Replica should be eagerly GC'ed as its peers tell it it's stale. This doesn't appear to be happening here (or my guess is wrong).
The text was updated successfully, but these errors were encountered: