You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say I have three logstash servers loadbalanced behind an F5. All three servers are identical, and contain an elasticsearch output plugin with a host array of something like: hosts => ["host1","host2",host3","host4"].
What I'm trying to prevent is a scenerio where the three logstash servers would get in a rhythm of rotating through the same hosts at the same time, thus swamping one elasticsearch host, while the others go unused.
From what I understand, an individual instance will round-robin through the array of available elasticsearch hosts. I believe I have experienced this scenario and was likely the cause of a backlog of unprocessed/dropped udp packets. I alleviated the issue by having each logstash instance only contain unique sets of hosts. i.e. logstash-1 would contain hosts => ["host1","host2"] and logstash-2 would contain hosts => ["host3","host4"]. This would not be the most ideal way of handling.