GC: remove compact on split (#18500)#18731
Conversation
|
@v01dstar This PR has conflicts, I have hold it. |
|
@ti-chi-bot: ## If you want to know how to resolve it, please read the guide in TiDB Dev Guide. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
4d36680 to
df85f93
Compare
8a3604c to
22690bc
Compare
close tikv#18451 Remove compaction scheduling on split key not found error. Split key not found error is usually returned when a region only has a few keys but a large number of stale MVCC versions. This was the incentive of scheduling a compaction on split error. However, this solution brings a more serious problem, i.e. worker threads starvation. We don't really need this extra compaction, we expect that, after the compaction optimization is done, this MVCC accumulation issue would be mitigated. So, once the "split key not found" occurs, we just rely on the CheckThenCompact to resolve it. Signed-off-by: Yang Zhang <yang.zhang@pingcap.com>
22690bc to
7c8f087
Compare
|
/test |
|
@v01dstar: The Use DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/test pull-unit-test |
|
/unhold |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Connor1996, v01dstar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
This is an automated cherry-pick of #18500
What is changed and how it works?
Issue Number: Close #18451
What's Changed:
Related changes
pingcap/docs/pingcap/docs-cn:Check List
Tests
Side effects
Release note