txn: workaround memdb panic#39741
Conversation
Signed-off-by: ekexium <eke@fastmail.com>
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
Signed-off-by: ekexium <eke@fastmail.com>
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 211e0c9 |
|
In response to a cherrypick label: new pull request created: #39757. |
TiDB MergeCI notify🔴 Bad News! New failing [2] after this pr merged.
|
Signed-off-by: ekexium eke@fastmail.com
What problem does this PR solve?
Issue Number: close #39611
Problem Summary:
This is only a workaround.
I think we should detach memdb tracker from the session tracker before we figure out the safe actions when exceeding quotaI discussed with @XuHuaiyu and decided to only work it around for now since previous
mem-quotamechanism doesn't find anomalies from TiDB's transaction part.What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.