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.

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

Fix the problem that statement being oom-killed within DoneAggressive Locking causing the transaction still in aggressive locking state (#1355) #1412

Conversation

MyonKeminta
Copy link
Contributor

This cherry-picks #1355 to tidb-8.1 branch.

…Locking causing the transaction still in aggressive locking state (tikv#1355)

* Quick fix the problem that statement being oom-killed within DoneAggressiveLocking causing the transaction still in aggressive locking state

Signed-off-by: MyonKeminta <[email protected]>

* Add comments to explain the change

Signed-off-by: MyonKeminta <[email protected]>

---------

Signed-off-by: MyonKeminta <[email protected]>
Co-authored-by: MyonKeminta <[email protected]>
@ti-chi-bot ti-chi-bot bot added the dco-signoff: yes Indicates the PR's author has signed the dco. label Aug 1, 2024
@cfzjywxk cfzjywxk merged commit f8e321f into tikv:tidb-8.1 Aug 1, 2024
10 checks passed
@MyonKeminta MyonKeminta deleted the m/quick-fix-oom-panic-on-done-aggressive-locking-8.1 branch August 1, 2024 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dco-signoff: yes Indicates the PR's author has signed the dco.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants