-
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: transfer-leases/quit failed [slow upreplication] #58492
Comments
@knz do you mind taking a look at this? It's unclear why node 3 was detected as dead, as I don't see any crashes in the logs. |
I recently found that the cluster monitor logic in roachtest may have a flaw. Maybe this is a smoking gun of that. Will investigate. |
@knz want to double check whether this issue should qualify as an alpha release blocker as well |
definitely not release blocker IMHO -- lease transfers that don't fully succeed during node restarts yield merely temporary inconvenience, and the issue is not new anyway |
@tbg I investigated this failure. It is expecting all leases to move out of some node (here, n3) and asserts this by checking, for every replicas on the node, that the lease is elsewhere. In this particular case, it appears that the lease for affected range Now I'd like to tweak the test so that it excludes ranges with invalid leases. How can I inspect whether leases are invalid using SQL? |
Sorry it took me so long to get back to you here. To the best of my knowledge, this is not possible. Do you feel that this test needs to remain a roachtest? As a roachtest, I would expect it to set up a workload and assert that the workload is not negatively impacted by the node draining. (Which, btw, is also a pain to set up in a roachtest, as you know, and we already have that roachtest: kv/gracefuldraining). Moreover, is this test adding enough value to be kept around, if we don't feel that it should remain a roachtest, assuming we get #59371 in? |
I agree that the structure of test is redundant with the code in #59371 However that other PR does not yet assert that all the leases have been transferred by a drain. We probably want to test that still. What would be a good non-SQL way to inspect whether all non-invalid leases have been transferred, and only invalid leases remain? |
That would be |
(roachtest).transfer-leases/quit failed on master@9fa4b125bfb07552b43ba4fd52c9301afd7a937b:
|
roachtest.transfer-leases/quit failed with artifacts on master @ 8009ac6bb63f455a18bb1139d505bdd9930816b7:
Reproduce
See the corresponding section in the [roachtest README](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/roachtest) |
roachtest.transfer-leases/quit failed with artifacts on master @ f19914b8c6281e463645580e1411774c3b0c20c9:
Reproduce
See the corresponding section in the [roachtest README](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/roachtest) |
roachtest.transfer-leases/quit failed with artifacts on master @ fe1fb73ae989142193643db30dd4b1b6dd6fe7dd:
|
roachtest.transfer-leases/quit failed with artifacts on master @ 701b177d8f4b81d8654dfb4090a2cd3cf82e63a7:
|
roachtest.transfer-leases/quit failed with artifacts on master @ 31af9e32a55a166166e9ba9c5327b7cd847ae236:
|
roachtest.transfer-leases/quit failed with artifacts on master @ c995342ead51e08f8ed1155de4218d30a00d86d2:
|
roachtest.transfer-leases/quit failed with artifacts on master @ 1c46e1cd4e5be986bf9d13799bb7e13ddc896ed2:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ eef03a46f2e43ff70485dadf7d9ad445db05cab4:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 6b8d59327add74cf1342345fb3eaffc3a3e765d2:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 50ef2fc205baa65c5a740c2d614fe1de279367e9:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ cab185ff71f0924953d987fe6ffd14efdd32a3a0:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 62ec88c61edcaa023a579199cc5b43d3ee951cef:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 847514dab6354d4cc4ccf7b2857487b32119fb37:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 3928f1963833fbf51ae47bd2a42ae6a200ebbb14:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 0880e83e30ee5eb9aab7bb2297324e098d028225:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ ee3efd6b1e24a3e1676778f5028fa0a35266f683:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ 04a41e7915f4a89dcc1d0dbd92466c6adf79ec9f:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
roachtest.transfer-leases/quit failed with artifacts on master @ dd82053908203cf6d77c36c06a8280831bb93d57:
Reproduce
See: roachtest README See: CI job to stress roachtests For the CI stress job, click the ellipsis (...) next to the Run button and fill in: * Changes / Build branch: master * Parameters / `env.TESTS`: `^transfer-leases/quit$` * Parameters / `env.COUNT`: <number of runs> |
I believe this has been fixed now: #68169 |
(roachtest).transfer-leases/quit failed on master@cee475331ca3629b503cd2e7c7919b72c98a5ca5:
More
Artifacts: /transfer-leases/quit
See this test on roachdash
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: