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
It will be nice if we could provide a comma or colon seperated url's in the requestUri. If the sink can do a round robin based load balancing between the two URI's that will be awesome. If it is already possible then please let me know.
The Elasticsearch Sink does that to some extent.
Quoting what the person said:
That is correct. The ES sink uses the connection pool functionality. So normally you pass in a couple of endpoints and the client is clever enough to check health and connect to the available one.
The text was updated successfully, but these errors were encountered:
A maintainer will be with you shortly, but first and foremost I would like to thank you for taking the time to report this issue. Quality is of the highest priority for us, and we would never release anything with known defects. We aim to do our best but unfortunately you are here because you encountered something we didn't expect. Lets see if we can figure out what went wrong and provide a remedy for it.
This falls into the same ballpark as #134 and #157. It's a network problem that easily can be solved at the network level. There already exists solutions for this, and because of that I'm closing this issue.
It will be nice if we could provide a comma or colon seperated url's in the requestUri. If the sink can do a round robin based load balancing between the two URI's that will be awesome. If it is already possible then please let me know.
The Elasticsearch Sink does that to some extent.
Quoting what the person said:
That is correct. The ES sink uses the connection pool functionality. So normally you pass in a couple of endpoints and the client is clever enough to check health and connect to the available one.
The text was updated successfully, but these errors were encountered: