Allow setHostWeight() to work before cluster is started. #27
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.
Currently, it requires starting the cluster first, which makes configuration
needlessly awkward:
In our use case, configuration is handled by a shared library, but when the
connection gets created is not under that library's control, so there's not
even an opportunity to call 3.
This modifies
setHostWeight()
to not fail if called bofer clusters have beeninitialised, and instead stores the configured weight in a static map. As new
clusters are created, they pull weights from that map when they have a matching
server.