[CELEBORN-1630] Support to apply ratis peer operation with RESTful api #2804
+969
−10
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
turboFei
changed the title
turboFei
changed the title
turboFei
changed the title
RexXiong
reviewed
Oct 15, 2024
| @@ -2655,6 +2657,14 @@ object CelebornConf extends Logging { | |||
| .timeConf(TimeUnit.SECONDS) | |||
| .createWithDefaultString("5s") | |||
|
|
|||
| val HA_MASTER_RATIS_LEADER_ELECTION_MEMBER_MAJORITY_ADD: ConfigEntry[Boolean] = | |||
There was a problem hiding this comment.
Maybe default as true is more reasonable then false, and do we need guarantee this value should be true? seems majority-add default is false in ratis.
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?
Sub task of CELEBORN-1628.
Mapping for below commands:
Why are the changes needed?
It is more convenient to apply the ratis operation with RESTful api.
Does this PR introduce any user-facing change?
No, new api.
How was this patch tested?
Integration testing. Will provide the screenshot
Add:
Remove:
Set peer priority:
