Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Enabling aggressive locking makes TestPointGetLockExistKey fail #41527

Closed
ekexium opened this issue Feb 16, 2023 · 0 comments · Fixed by #41528
Closed

Enabling aggressive locking makes TestPointGetLockExistKey fail #41527

ekexium opened this issue Feb 16, 2023 · 0 comments · Fixed by #41528
Labels
affects-6.6 severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@ekexium
Copy link
Contributor

ekexium commented Feb 16, 2023 •
edited
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

set @@tidb_pessimistic_txn_aggerssive_locking=1 in test TestPointGetLockExistKey

2. What did you expect to see? (Required)

test pass.

3. What did you see instead (Required)

error: pessimistic lock not found for RC isolation level.

4. What is your TiDB version? (Required)

master (v6.6.0)
@ekexium ekexium added type/bug The issue is confirmed as a bug. affects-6.6 labels Feb 16, 2023
@ekexium ekexium changed the title Enabling aggressive locking make test TestPointGetLockExistKey fail Enabling aggressive locking makes TestPointGetLockExistKey fail Feb 16, 2023
@ekexium ekexium mentioned this issue Feb 16, 2023
Merged
12 tasks
@ti-chi-bot 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.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 may-affects-6.5 labels Feb 17, 2023
@aytrack aytrack added the sig/transaction SIG:Transaction label Feb 17, 2023
@ekexium ekexium 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.0 may-affects-6.1 may-affects-6.2 may-affects-6.3 may-affects-6.4 may-affects-6.5 labels Feb 22, 2023
ti-chi-bot pushed a commit that referenced this issue Feb 22, 2023
@ekexium
txn: fix point-lock non-existent key with aggressive locking under rc (…
f931359 
…#41528)

close #41527
@cfzjywxk cfzjywxk mentioned this issue Mar 23, 2023
Merged
15 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-6.6 severity/major sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

txn: fix point-lock non-existent key with aggressive locking under rc ekexium/tidb
3 participants
@aytrack @ekexium @ti-chi-bot