[IOTDB-4366] Fix Ratis 1 replica migrate error; terminate the RegionMigrationProcedure process when datanode report failure result#7269
Merged
qiaojialin merged 20 commits intomasterfrom Sep 15, 2022
Conversation
|
SonarCloud Quality Gate failed. |
qiaojialin
approved these changes
Sep 15, 2022
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
Two improvements:
executing remove-datanode.sh for Ratis 1 replica will be failed in the

deleteOldRegionstep, so we cancel the step ofdeleteOldRegionin RegionMigrateProcedure in the case of Ratis 1 replica.RegionMigrateProcedure step will be terminated when the datanode reported failed.

The test running results are as below.
SchemaRegion=Ratis, DataRegion=Ratis
Before remove datanode:

After remove the datanode 0.0.0.0:6669

jps result:

