I deployed Elasticsearch on Kubernetes and it's working fine. Also, I created an ingress so it's redirecting from 80 => 9200. But logstash is looking for 9200 so connection is failing.
Hi @Badger
when I update conf with :80 instead of :9200
at first it connected. here is the log
[2020-07-14T20:18:13,047][WARN ][logstash.licensechecker.licensereader] Restored connection to ES instance {:url=>"http://elastic:xxxxxx@elasticsearch.phoenix-alfresco.10.85.77.116.xip.io:80/"}
and then immediately I see this updating. log:
[2020-07-14T20:18:17,864][INFO ][logstash.outputs.elasticsearch][main] Elasticsearch pool URLs updated {:changes=>{:removed=>[], :added=>[http://elastic:xxxxxx@elasticsearch.phoenix-alfresco.10.85.77.116.xip.io:9200/]}}
I believe this is x-pack issue. Any suggestions here ?
As you said changing the elasticsearch output in logstash.yml file to http://elasticsearch_url:80 solved this issue. So far I have been updating it in logstash.conf file.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.