-
Notifications
You must be signed in to change notification settings - Fork 5.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
txn: the update could not read the latest data if read committed is used. #41581
Labels
Comments
cfzjywxk
added
type/bug
The issue is confirmed as a bug.
severity/critical
affects-6.0
affects-6.1
labels
Feb 20, 2023
ti-chi-bot
added
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.2
may-affects-6.3
may-affects-6.4
may-affects-6.5
may-affects-6.6
labels
Feb 20, 2023
cfzjywxk
removed
may-affects-4.0
This bug maybe affects 4.0.x versions.
may-affects-5.1
This bug maybe affects 5.1.x versions.
may-affects-5.2
This bug maybe affects 5.2.x versions.
may-affects-5.3
This bug maybe affects 5.3.x versions.
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-5.0
This bug maybe affects 5.0.x versions.
may-affects-6.2
may-affects-6.3
may-affects-6.4
may-affects-6.5
may-affects-6.6
labels
Feb 20, 2023
I think 07b0c7c introduces this bug. |
4 tasks
ti-chi-bot
pushed a commit
that referenced
this issue
Feb 21, 2023
cfzjywxk
added a commit
to cfzjywxk/tidb
that referenced
this issue
Feb 21, 2023
12 tasks
zhangjinpeng87
pushed a commit
that referenced
this issue
Feb 21, 2023
close by #41590 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
2. What did you expect to see? (Required)
3. What did you see instead (Required)
The update could not read the latest data, this is possibly a bug introduced during the refactoring of the transaction module in tidb, after #34702 the bug is fixed, but v6.1.x and v6.0.0 are affected.
4. What is your TiDB version? (Required)
tidb v6.0.0 v6.1.x
The text was updated successfully, but these errors were encountered: