# Logstash -\> Elastic Timeouts

**URL:** <https://discuss.elastic.co/t/logstash-elastic-timeouts/312713>\
**Category:** Logstash\
**Created:** [August 23, 2022, 1:57pm UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713 "2022-08-23T13:57:12Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![6igwig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/6igwig/32/88971_2.png) [@6igwig](https://discuss.elastic.co/u/6igwig)\
**Post date:** [August 23, 2022, 1:57pm UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/1 "2022-08-23T13:57:12Z")

</div>

I have 2 logstash nodes with about 30 different pipelines sending data to a 6 node elastic cluster. For about half of my pipelines I am seeing a ton of errors like this in the /var/log/logstash/pipeline\_mypipeline.log files:

`[WARN][logstash.outputs.elasticsearch] Marking url as dead. Last error: [LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError] Elasticsearch Unreachable: [https://node1.mynetwork.com:9200/_bulk][Manticore::SocketTimeout] Read timed out` and `[ERROR][logstash.outputs.elasticsearch] Attempted to send a bulk request but Elasticsearch appears to be unreachable or down {:message=>"Elasticsearch Unreachable: [https://node1.mynetwork.com:9200/_bulk][Manticore::SocketTimeout] Read timed out"`

My data is ingesting fine. I suppose once a node times out then logstash moves on to another one, but I would like to handle these messages. Some are labeled as "WARN" and others are "ERROR". I see the elasticsearch output has a [timeout](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html#plugins-outputs-elasticsearch-timeout) parameter. Bumping that up to 2 minutes instead of 1 might do the trick but that seems more like avoiding the problem instead of handling it.

I have a monitoring cluster set up. My cluster health is green, every node has plenty of free space, cpu is around 20%... For the logstash nodes their CPU is low (5%), JVM heap averages around 6.1GB out of 7.9GB.

What should I look at to address timeout warnings / errors like these?

---

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [August 23, 2022, 2:31pm UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/2 "2022-08-23T14:31:21Z")

</div>

Hello,  
Could you please paste your elastic output from logstash conf file?

---

<div class="post-metadata">

**Author:** ![6igwig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/6igwig/32/88971_2.png) [@6igwig](https://discuss.elastic.co/u/6igwig)\
**Post date:** [August 23, 2022, 4:52pm UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/3 "2022-08-23T16:52:01Z")

</div>

```auto
output {
    elasticsearch {
        hosts => ["https://node1.mynetwork.com:9200", "https://node2.mynetwork.com:9200", ...]
        manage_template => false
        index => "%{[@metadata][target_index]}"
        pipeline => "xdr-all"
        user => "${xdr_user}"
        password => "${xdr_password}"
        document_id => "%{log.fingerprint}"
        ssl => true
        cacert => '/etc/certificates/logstash/my-cert.pem'
        data_stream => "false"
    }
}

```

---

<div class="post-metadata">

**Author:** ![sudhagar\_ramesh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sudhagar_ramesh/32/105673_2.png) [@sudhagar\_ramesh](https://discuss.elastic.co/u/sudhagar_ramesh)\
**Post date:** [August 25, 2022, 4:01am UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/4 "2022-08-25T04:01:53Z")

</div>

Hello @6igwig

The log clearly shows that the below host is unreachable, could you check whether the node is up or not?

[https://node1.mynetwork.com:9200](https://node1.mynetwork.com:9200)

---

<div class="post-metadata">

**Author:** ![6igwig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/6igwig/32/88971_2.png) [@6igwig](https://discuss.elastic.co/u/6igwig)\
**Post date:** [August 25, 2022, 4:00pm UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/5 "2022-08-25T16:00:29Z")

</div>

The node is up

---

<div class="post-metadata">

**Author:** ![cheshirecat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cheshirecat/32/109532_2.png) [@cheshirecat](https://discuss.elastic.co/u/cheshirecat)\
**Post date:** [August 26, 2022, 7:17am UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/6 "2022-08-26T07:17:13Z")

</div>

Maybe node is up but how about FW?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 23, 2022, 7:17am UTC](https://discuss.elastic.co/t/logstash-elastic-timeouts/312713/7 "2022-09-23T07:17:15Z")

</div>

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