Repository navigation
[To dev/1.3] Fix duplicate DataRegion scheduling after recovery - #19065
Merged
shuwenwei merged 1 commit intoOct 30, 2026
Merged
Conversation
(cherry picked from commit 0ee8191)
shuwenwei
approved these changes
Oct 30, 2026
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
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
Backport #18803 to
dev/1.3.During restart recovery, a DataRegion with no asynchronous TsFile resource recovery tasks already initializes compaction scheduling in synchronous recovery. The subsequent asynchronous recovery flow initializes it again, creating duplicate entries shared by TTL and compaction scheduling.
Skip that flow for empty task lists, make registration atomic and idempotent under the existing Vector monitor, and remove every occurrence of the same DataRegion on unregistration. Preserve dev/1.3's existing compaction-disable behavior when resolving the cherry-pick conflict; the
setAllowCompaction(false)context line in master was not part of #18803's change.