Introduce a target cluster size hint setting #3635
Merged
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
dcorbacho
approved these changes
Nov 3, 2021
|
@Mergifyio rebase |
|
Rebasing to pick up CI fixes |
This is meant to be used by deployment tools, core features and plugins that expect a certain minimum number of cluster nodes to be present. For example, certain setup steps in distributed plugins might require at least three nodes to be available. This is just a hint, not an enforced requirement. The default value is 1 so that for single node clusters, there would be no behavior changes.
pjk25
force-pushed
the
mk-cluster-formation-target-cluster-size-hint
branch
from
0d8b754
to
686dccf
Compare
✅ Branch has been successfully rebased |
michaelklishin
deleted the
mk-cluster-formation-target-cluster-size-hint
branch
michaelklishin
added a commit
that referenced
this pull request
Nov 3, 2021
Introduce a target cluster size hint setting (backport #3635)
michaelklishin
added a commit
that referenced
this pull request
Nov 3, 2021
…uster-size-hint Introduce a target cluster size hint setting (cherry picked from commit 054b7e4) Conflicts: deps/rabbit/src/rabbit_nodes.erl
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.
This is meant to be used by deployment tools,
core features and plugins that expect a certain minimum
number of cluster nodes to be present.
For example, certain setup steps
in distributed plugins might require
at least three nodes to be available.
This is just a hint, not an enforced
requirement. The default value is 1
so that for single node clusters,
there would be no behavior changes.