executor: handle OOM panic which not be recovered now in distSQL layer #10544
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qw4990
changed the title
|
/rebuild |
qw4990
changed the title
|
/run-all-tests |
winkyao
added
the
priority/release-blocker
|
/run-all-tests |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
In order to control memory consumption in distSQL layer, we let
SelectResultandcopWorkeruseMemTrackerto trace and control their memory.When memory consumption exceed the quota,
MemTrackerwill panic butSelectResultandcopWorkerdon't handle this panic rightly which may cause TiDB exit.What is changed and how it works?
Add some recover statements to handle panic.