Fix Compaction Schedule didn't start#11439
Merged
xingtanzjr merged 3 commits intomasterfrom Oct 31, 2023
Merged
Conversation
xingtanzjr
approved these changes
Oct 31, 2023
|
SonarCloud Quality Gate failed.
|
xingtanzjr
pushed a commit
that referenced
this pull request
Nov 21, 2023
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
2 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.
Description
#11421 tried to start the CompactionSchedule of each data region after all data regions recovered. However, the previous implement didn't make sure all data region recovered before init Compaction Schedule. Besides, some recovering data regions may not init Compaction Schedule.
This PR is moving the initCompactionSchedule to the recoverEndTrigger Thread where we can know the recover status of all data regions.