-
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: restart/down-for-2m failed #44060
Comments
(roachtest).restart/down-for-2m failed on release-19.1@a8444e28d3e7bf07c8ee0c6d5809e7466b57f6f9:
|
(roachtest).restart/down-for-2m failed on master@e671a4ef97cbc6cf5d22f8f322fd45733d302094:
|
cc @andreimatei |
This last crash should be fixed by #45102 |
(roachtest).restart/down-for-2m failed on master@954fe69d554162aec0fbc001aad1fe5103d8df13:
|
(roachtest).restart/down-for-2m failed on master@752dea867f3aeb142e98c22f8d320ce19041aa8d:
|
(roachtest).restart/down-for-2m failed on master@dfa5bd527ae7d7373dd03c62118df87a87a77130:
|
(roachtest).restart/down-for-2m failed on master@c473f40078994551cebcbe00fdbf1fa388957658:
|
(roachtest).restart/down-for-2m failed on master@72c4a1bd411f2f82bf9aaa22883821a946614148:
|
(roachtest).restart/down-for-2m failed on master@69dc87d68addedf2fabfb2b14c098cfb35b5f3d0:
|
(roachtest).restart/down-for-2m failed on master@33d71472dc01cbc5064b3c5e1fcd666a33f606de:
|
(roachtest).restart/down-for-2m failed on master@5a3d0c9539a671f0e55b680d3021b18dde9d190d:
|
(roachtest).restart/down-for-2m failed on master@b5f030223fbcf22e806c48a3c46e74a73a54f50f:
|
This doesn't look like anything we're aware of. In the last two failures, we see node 3 stall while being started:
I don't see anything in the logs that immediately makes it clear what's going wrong. We'll need to take a closer look into this. |
The test is stuck here: cockroach/pkg/cmd/roachtest/restart.go Lines 75 to 77 in 8e4d7b2
#45887 was supposed to give us the server side of the hang, but it doesn't seem to have done that (the roachprod logs confirm that we did send SIGSEGV). |
From debug zip queries:
def something stuck on the KV side:
There's nothing stuck in a
We're probably caught in some infinite retry loop. The only other goroutine anchored in
which is similarly not stuck, but has likely been retrying for a long time. |
Closing due to inactivity. We're not sure what fixed this, but it used to fail very regularly. |
(roachtest).restart/down-for-2m failed on master@e2c2be6cbef07c7f2ee6341816f81f72a206c32a:
Repro
Artifacts: /restart/down-for-2m
powered by pkg/cmd/internal/issues
The text was updated successfully, but these errors were encountered: