-
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
roachtest: restore/nodeShutdown/coordinator failed #85879
Comments
Under the hood, from
|
Even further under the hood, this appears to be an issue from AdminSplit. We think #85405 may help. Reassigning to KV in case more work is needed. |
I don't think this is the same as the issue that is fixed by #85405, though it is related. What we see here is that we're trying to trying to exit a joint configuration and are hitting an error because the current leaseholder is still a Next steps:
|
Include information about the replica that is returning the error and about the current range descriptor. Related to cockroachdb#85879. Release justification: low risk, improves debugging.
86319: kv: improve IllegalReplicationChangeError r=nvanbenschoten a=nvanbenschoten Include information about the replica that is returning the error and about the current range descriptor. Related to #85879. Release justification: low risk, improves debugging. 86414: build: bump Pebble metamorphic test duration r=nicktrav a=jbowens Increase the Pebble metamorphic test duration to 6h. We want the increase test coverage at least for the duration of stability. Release justification: Non-production code changes Release note: None 86418: tree: optimize AvailableTypes r=ajwerner a=ajwerner Check out this profile from `@msirek:` ![pasted image 0](https://user-images.githubusercontent.com/1839234/185487480-4f33551c-ce0e-4d74-91c7-ab15c101f4dd.png) Release justification: Minor change with no impact on correctness Release note: None Co-authored-by: Nathan VanBenschoten <[email protected]> Co-authored-by: Jackson Owens <[email protected]> Co-authored-by: Andrew Werner <[email protected]>
Include information about the replica that is returning the error and about the current range descriptor. Related to #85879. Release justification: low risk, improves debugging.
roachtest.restore/nodeShutdown/coordinator failed with artifacts on release-22.1 @ 714fa0ad80c499cbd96ba97c560a9b414c61104f:
Same failure on other branches
|
roachtest.restore/nodeShutdown/coordinator failed with artifacts on release-22.1 @ f0da2ccc9f3641e4b8252dced7b3c42dca2f2dc1:
Same failure on other branches
|
roachtest.restore/nodeShutdown/coordinator failed with artifacts on release-22.1 @ 9eb4da2a351b2fe4706be9aa4af27ee2e60b405e:
Same failure on other branches
|
roachtest.restore/nodeShutdown/coordinator failed with artifacts on release-22.1 @ a769b09b2f664a04b5bf513a12eb21bdbfdb7ca3:
Same failure on other branches
|
roachtest.restore/nodeShutdown/coordinator failed with artifacts on release-22.1 @ e8a6797dd6b1482b740c7c9ec681a5e84dd8a8d8:
Help
See: roachtest README
See: How To Investigate (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-18473
The text was updated successfully, but these errors were encountered: