-
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
ccl: TestCCLLogic occasionally gets stuck #83630
Comments
There's some interesting things in the logs you uploaded. The test is stuck in cluster creation. This is a tenant test. It is stuck setting a cluster setting:
cockroach/pkg/sql/logictest/logic.go Lines 1893 to 1895 in 0917fdc
Looking a bit deeper, it appears to be some sort of deadlock. One thing which stuck out to me is that one of the transaction is trying to write an event log. One observation is that the transaction handling inside of the cluster settings code is a little bit surprising and opaque. There's a restriction that you not set cluster settings in an explicit or multi-statement transaction presumably to support manual transaction management here: cockroach/pkg/sql/set_cluster_setting.go Line 305 in a5e3f4a
The transaction which appears blocked is actually underneath the |
Oh, I should note it's writing a cluster setting to the system tenant IIUC. |
Solved by 139dc42. |
I've been trying to figure out the cause of the increase in "Execution timeouts" (here you can see the failures on the staging branch). I think I ran into three such timeouts manually, on the gceworker.
First time on
CREATE UNIQUE INDEX idx_uniq_hash_email ON t_unique_hash_sec_key (email) USING HASH;
inregional_by_row_hash_sharded_index_query_plan
.Second time on
CREATE INDEX ON t_to_be_hashed (b) USING HASH;;
inregional_by_row_hash_sharded_index
.Third time on
Unfortunately, I only have the logs for the third failure (first two were through bazel that doesn't dump the goroutines). Here is the log from the third timeout.
ccl.zip
I didn't analyze this log, but this seems like a schema-related issue, so putting it into the corresponding project board.
Jira issue: CRDB-17180
The text was updated successfully, but these errors were encountered: