-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
update with point-get plan maybe panic cause use different infoschema. #41622
Comments
I guess all the The result of Lines 3976 to 3997 in 4ac7dc9
Line 84 in 4ac7dc9
tidb/sessiontxn/isolation/base.go Lines 141 to 153 in 4ac7dc9
|
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
The original failed test link: https://do.pingcap.net/jenkins/blue/organizations/jenkins/pingcap%2Ftidb%2Fghpr_check2/detail/ghpr_check2/14634/pipeline/201/
Then I try to reproduce, and I add following log and sleep in my code for easier reproduction:
Then run the test:
start a real tikv first:
Then run the test, repeat it a few times, it should be easier to reproduce:
When reproduced, you will see the following log:
Pay attention to this log:
this log indicates the update with point-get plan use different infoschema, when the update use
tryPointGetPlan
to build point-get, it use infoschema version-1 which can only see 2 columns of tablet
.But later the update use
buildPointUpdatePlan
to build point-update, it use infoschema version-2 which can see 3 columns of the tablet
. This is what causes panic3. How to fix?
make sure update with point-get plan always use the same version of infoschema.
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: