-
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
executor: add an OOMAction for copIterator to adaptive control the memory usage #19246
Conversation
@Yisaer can we reduce the log size? |
updated, the unnecessary log param is removed now. |
/run-unit-test |
LGTM |
/run-all-tests |
/run-all-tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Almost LGTM
LGTM |
/merge |
/run-all-tests |
@Yisaer merge failed. |
/run-tics-test |
@Yisaer Could you prepare a detailed test report for this PR? We may need to consider these parts:
|
got it. |
What problem does this PR solve?
Currently TableReader will consume too much memory and have no oom action.
Issue Number: close #xxx
ref #16104
What is changed and how it works?
Add one oom action for the coprocessor in non keep-order case. As copIterator in non keepOrder case have already supported sendRate. The oom action strategy is to reduce the sendrate ticket and drain out copResponse in response channel while the copWroker have been suspended when the oom action have been triggered.
If the ticket for the sendrate have been reduced to 1 , the oom action will delegate to the fallback action.
Here is the memory status for backuping 200G data with v4.0.2 PD and TIKV
logs during backup
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Release note