[Region Migration] Set TTL After Add Region Peer #12603
Closed
Conversation
This file contains 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
liyuheng55555
suggested changes
May 28, 2024
...onfignode/src/main/java/org/apache/iotdb/confignode/procedure/env/RegionMaintainHandler.java
Outdated
Show resolved
Hide resolved
|
Each node in the device TTL has its full information cached independently by DataNodeTTLCache, which is irrelevant to region migration, so this problem does not exist and this PR will be closed. |
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
Set TTL during the region migration may failed because the concurrency issue of createRegion and SET TTL operation.
The solution is to update the TTL after the Add Region Peer phase is completed.
See details in feishu