HDDS-11799. Remove hdds.scm.safemode.pipeline-availability.check property #8095
+48
−124
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
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.
What changes were proposed in this pull request?
The Pipeline creation logic has changed a lot from the time "hdds.scm.safemode.pipeline-availability.check" property was introduced. Now we create the pipelines in background, so the Pipeline Rule will not block safemode exit even in a fresh cluster.
This property is not need now.
This is why this property was added : Since in a real cluster we may not have a open pipeline in beginning, this rule should be turned off by default.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11799
How was this patch tested?
CI:
https://github.com/peterxcli/ozone/actions/runs/13878915745