-
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
Deadlock in SHOW TABLES #44385
Comments
FYI: This issue is slowing down my testing efforts, since I can only use a single thread to test CockroachDB. |
I'm looking at the goroutine dump. looks like the
is conflicting with the information_schema lookup for
|
@ajwerner any thoughts on this? |
also scarily after this happens, after restarting |
Well one thing to note is that this is pretty new. I can't repro on 19.2.3 but it seems to repro instantly on master. |
Well this one is super duper fun! and indicative of problems lurking in the deep. The problem seems to be that we have a My one remaining question is whether the interaction with caches has changed in such a way that this case is now much more common. The recommended solution is to force the connExecutor to abandon the current transaction and cleanup its intents when retrying a transaction which performs any DDLs. For now let's fold these deadlocks into the below issue: |
It seems that
SHOW TABLES
in combination with other concurrent requests can result in a deadlock. This can be reproduced by executing these commands, as demonstrated below:I found this issue using
2c4c0f92b8d137054e03872e6503561465f55eee
.UPDATE: While I initially reported this issue privately, I now included all the information as part of this bug report, since the issue does not seem to be security-relevant.
The text was updated successfully, but these errors were encountered: