-
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
*: global memory controller should not kill session whose mem less than limit_sess_min_size #42803
Conversation
…an limit_sess_min_size
[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. Reviewer can indicate their review by submitting an approval review. |
memUsage := t.BytesConsumed() | ||
// If the memory usage of the top1 session is less than tidb_server_memory_limit_sess_min_size, we do not need to kill it. | ||
if uint64(memUsage) < limitSessMinSize { | ||
memory.MemUsageTop1Tracker.CompareAndSwap(t, nil) |
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.
If CompareAndSwap fails, it means the Top1Tracker is another tracker now, but we will skip the check and kill in this round, right?
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.
It looks OK, I see the interval is 100 ms.
executor/executor_test.go
Outdated
@@ -6481,3 +6481,46 @@ from ssci right join csci on (ssci.customer_sk=csci.customer_sk | |||
and ssci.item_sk = csci.item_sk) | |||
limit 100;`) | |||
} | |||
|
|||
func TestIssue42662(t *testing.T) { |
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.
Because too many test cases are in the executor. Please move it into executor/issuetest
.
on the other hand, TestIssuexxxx
makes people wonder what exactly has been repaired.
/retest |
/retest |
1 similar comment
/retest |
/retest |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: ff2bef0
|
In response to a cherrypick label: new pull request created to branch |
Signed-off-by: ti-chi-bot <[email protected]>
What problem does this PR solve?
Issue Number:
close #42662
close #42664
Problem Summary:
As the description mentioned here:
#42662 (comment)
What is changed and how it works?
Check List
Tests
If we run the same test on master branch, the following error will be thrown:
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.