Oliver Eilhard
Oliver Eilhard
Hmm... if I understand it correctly, with AWS you should simply disable sniffing and health checks as AWS does load-balancing for you, _and_ you should simply use the hostname provided...
Hmm... let's see. First of all, the whole idea of sniffing and health checks is only necessary because in the early days of ES, load-balancing was done client-side. If you...
I changed the docs in the Wiki and advised to disable both sniffing and health checks for AWS Elasticsearch Service.
Maybe there's still a problem. Reopening.
There was a change quite recently that addresses an issue on AWS ES with nodes changing IPs particularly. Don't know if this has anything to do with it. https://github.com/olivere/elastic/pull/1125
Thanks for reporting your findings, @g-wilson.
@Sovietaced I'm not sure that's correct. Sniffing is a process by which the client library asks the ES cluster (not the DNS) for the IP addresses of the nodes, then...
Interesting. Maybe we should accommodate to that and—at least—log a warning. I will have to test this out on AWS ES.
Thanks for the links. Very helpful.
I've been looking into this and am experimenting with an additional `elastic.SetCloseIdleConnections(true|false)` configuration option for `elastic.NewClient`. When enabled, the `PerformRequest` method will automatically close idle connections in the underlying HTTP...