feat(helm): Allow configuring max-join-peers #2406
Open
+11
−1
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
Btw, do you have any documentation on recommended max peers and the resource impact increasing the max limit does? I assume with clustering set by default to 5 and using clustering ends with a lot of duplicated targets?
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.
PR Description
Allow setting
--cluster.max-join-peers.Do you have any documentation on recommended max peers and the resource impact increasing the max limit does? Is a cluster with 20/30 peers already too many or is it in the 100s?
I assume with clustering set by default to 5 and using clustering ends with a lot of duplicated targets?
I get a lot of:
Which issue(s) this PR fixes
Notes to the Reviewer
PR Checklist