fix the problem that expired data was not recycled timely due to slow gc speed (#4224)#4253
Closed
ti-chi-bot wants to merge 1 commit intopingcap:release-5.2from
Closed
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
Member
Author
|
[REVIEW NOTIFICATION] This pull request has not been approved. 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. |
12 tasks
Contributor
|
This change is merged into #3695. Close it. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This is an automated cherry-pick of #4224
What problem does this PR solve?
Issue Number: close #4146
Problem Summary: The current gc speed is too slow and the data cannot be reclaimed timely when corresponding region was scheduled to other nodes.
What is changed and how it works?
Check List
Tests
Side effects
Documentation
Release note