UNEXPECTED POOL ERROR but logstash is pushing to Elastic perfectly fine?

Hi, running Logstash 6.2.4 in docker container with DC/OS marathon.

I have logstash ingesting logs from Kafka and pushing to my cluster perfectly fine!!! But in the logs I see these every few seconds and it also seems to restore every attempt.

[2018-06-15T21:31:48,524][WARN ][logstash.outputs.elasticsearch] UNEXPECTED POOL ERROR {:e=>#<LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError: No Available connections>}
[2018-06-15T21:31:48,525][ERROR][logstash.outputs.elasticsearch] Attempted to send a bulk request to elasticsearch, but no there are no living connections in the connection pool. Perhaps Elasticsearch is unreachable or down? {:error_message=>"No Available connections", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError", :will_retry_in_seconds=>4}
[2018-06-15T21:31:49,768][INFO ][logstash.outputs.elasticsearch] Running health check to see if an Elasticsearch connection is working {:healthcheck_url=>http://esdev.marathon.l4lb.thisdcos.directory:9200/, :path=>"/"}
[2018-06-15T21:31:49,773][WARN ][logstash.outputs.elasticsearch] Restored connection to ES instance {:url=>"http://esdev.marathon.l4lb.thisdcos.directory:9200/"}

ok so esdev.marathon.l4lb.thisdcos.directory is a load balanced virtual i.p!

I'm guessing it's changing I.P constantly for logstash. So it think it's lost the connection?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.