-
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
prepare statement can't receive schema update #25482
Comments
Can not reproduce. My output:
Don't know why though, the problem of prepare does exist. |
@xhebox to reproduce, you show run the two rename ddl separately, run the first rename, wait until the error occurred, and then run the second. it is expected that the error will disappear after the second ddl, but it doesn't. |
@xhebox and I found it can be reproduced on v4.0.11, but not master. |
and on |
sorry, this is my local development commit, the merge-base between it and master is
and it can be reproduced on the merge-base. |
Why it can be reproduced on v4.0.11? I thought the problem is introduced by me. But I never cherry-pick them back to 4.0. |
I think the problem exists already before your change |
and you happens to fixed it in bfdad7c#diff-10dab83c04a99358d431906d37f48b92be97d50a2719d4ddf81c62d3b03a0aebR2883-R2895 |
do you have any suggestions for the fix on v4.0.11? |
OK, I remembered the case. Here is the issue, #24233. And it is not cherry-picked because they worry about the stability of these 3 PRs. These PRs are developed as some fixes for stale read feature. By 3 PRs, I finally get most operations of getting infoschema consistent, and the problem may come from some inconsistent behaviors fixed by PRs. Maybe cherry-icking all 3 PRs will fix the problem... |
@xhebox would you like to take over this issue? |
Is it urgent? I don't think I have time today or tomorrow. |
nope, you can do it any time in the future (better before next 4.x release)
…On Thu, Jun 17, 2021 at 5:18 PM xhe ***@***.***> wrote:
Is it urgent? I don't think I have time today or tomorrow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#25482 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHC3V5N2EZEQCBIMXT65H6TTTG4XNANCNFSM46Y5T6AA>
.
|
/assign @xhebox |
have been fixed in 5.1 |
Please edit this comment or add a new comment to complete the following informationNot a bug
Duplicate bug
BugNote: Make Sure that 'component', and 'severity' labels are added 1. Root Cause Analysis (RCA) (optional)2. Symptom (optional)3. All Trigger Conditions (optional)4. Workaround (optional)5. Affected versions6. Fixed versions |
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
start a session, execute:
then, using the following code to connect
while the above code is executing, rename the 2 tables in another session
2. What did you expect to see? (Required)
No error.
3. What did you see instead (Required)
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: