-
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
txn: memory of previous execution can not be released when retrying a transaction #56837
Comments
Related issue tikv/client-go#1375. |
After some discussions, the issue would be fixed in the release versions, changing the label to "bug". For versions >= v8.4, the issue is already fixed as the new ART memdb is used by default instead of the red-black tree one. For versions < v8.4, the fix would be picked for RB-tree memdb, the solution is:
|
close #1375, ref pingcap/tidb#56837 Signed-off-by: you06 <[email protected]> Co-authored-by: cfzjywxk <[email protected]>
Enhancement
When retrying a transaction, for example, when we meet lock-conflict error, the memory of the previous execution can not be released until the txn commits successfully. It may cause conflict txn killed by tidb_mem_quota_query or make TiDB OOM
This issue was fix in tikv/client-go#1451 since v8.4.0, while I think we need PR to fix it in lower versions.
The text was updated successfully, but these errors were encountered: