Clarify load balance behavior if array of hosts is used #866
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
I've seen the question, on how the output load balances, coming up every now and then and the docs should have the answer. I'd still like a logstash developer to review and double check that it still is Round-robin per bulk in the current version of the plugin. My assumption is based on #274 and #493 (comment), but the first one is from 2015 and the second onw is from 2018, but with Logstash 2.4.
|
Have there been any updates on that? |
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.
I've seen the question, how the output load balances, coming up every now and then and the docs should have the answer.
I'd still like a logstash developer to review and double check that it still is Round-robin per bulk in the current version of the plugin.
My assumption is based on #274 and #493 (comment), but the first one is from 2015 and the second onw is from 2018, but with Logstash 2.4.