Allow Optional Configuration of Max Clone Count #25
Conversation
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
Allows the user to optionally change the max clone count from the default of 100 to a value of their choosing via the net.spy.maxCloneCount property. This enhancement is useful for applications that have a large number of endpoints and want to use the Redistribute FailureMode, but also want to limit the number of cloning opportunities (as 100 is fairly high for a high throughput usecase).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Allows the user to optionally change the max clone count from the
default of 100 to a value of their choosing via the
net.spy.maxCloneCount property. This enhancement is useful for
applications that have a large number of endpoints and want to use
the Redistribute FailureMode, but also want to limit the number of
cloning opportunities (as 100 is fairly high for a high throughput
usecase).