Hi good day community:
I would like to ask if someone that you it has experiment this behavior:
We have 4 servers with instances of logstash with version 7.9, into config file into output to Elasticsearch, we have 12 servers, we are having a issue the service restart many time when 2 of 12 nodes into Elasticsearch is down or unavailable, these Elasticsearch instances could be on maintenance, we have the 10 rest continue working. we are getting the attached error.
Also I am attaching the output section of config file:
output { elasticsearch { hosts => [ "https://10.34.31.134:9299","https://10.34.31.135:9299","https://10.34.31.136:9299","https://10.34.31.137:9299","https://10.34.31.138:9299","https://10.34.31.139:9299","https://10.34.31.140:9299","https://10.34.31.141:9299","https://10.34.31.142:9299","https://10.34.31.143:9299","https://10.34.31.144:9299","https://10.34.31.145:9299" ] ilm_enabled => true ilm_pattern => "000001" ilm_policy => "puppet_XXXXX" ilm_rollover_alias => "ilm-XXXX" user => "logstash" password => "XXXXXXXXXXXX" ssl_certificate_verification => false cacert => "/etc/logstash/root-ca.pem" manage_template => false } }
{"level":"FATAL","loggerName":"logstash.runner","timeMillis":1602192926037,"thread":"LogStash::Runner","logEvent":{"message":"An unexpected error occurred!","error":{"metaClass":{"metaClass":{"metaClass":{"error":"Could not reach host Manticore::SocketException: Connection refused (Connection refused)","backtrace":["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:334:in perform_request_to_url'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:319:in block in perform_request'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:414:in with_connection'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:318:in perform_request'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:326:in block in get'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:162:in get'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/http_client.rb:378:in get_xpack_info'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/ilm.rb:57:in ilm_ready?'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/ilm.rb:28:in ilm_in_use?'","/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.6.2-java/lib/logstash/outputs/elasticsearch/common.rb:50:in block in setup_after_successful_connection'"]}}}}}}