# Ingest Node Pipelines making Elasticsearch Unreachable

**URL:** <https://discuss.elastic.co/t/ingest-node-pipelines-making-elasticsearch-unreachable/253534>\
**Category:** Elasticsearch\
**Created:** [October 28, 2020, 8:47am UTC](https://discuss.elastic.co/t/ingest-node-pipelines-making-elasticsearch-unreachable/253534 "2020-10-28T08:47:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vijay\_Barai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijay_barai/32/76087_2.png) [@Vijay\_Barai](https://discuss.elastic.co/u/Vijay_Barai)\
**Post date:** [October 28, 2020, 8:47am UTC](https://discuss.elastic.co/t/ingest-node-pipelines-making-elasticsearch-unreachable/253534/1 "2020-10-28T08:47:48Z")

</div>

I am using ES-7.9.1. I created few ingest pipeling for small enrichment using UI. All pipeline working fine individually when load a data using logstash-output-elasticsearch. To impliment all the enrichment I combined 5 ingest pipeling into single pipeline and used it in logstash-output-elasticsearch plugin.  
But getting following error.

```auto
[2020-10-28T08:28:14,042][WARN][logstash.outputs.elasticsearch][main][8b15d2eec22acf181b52840d4936ea5f6a231ac7026b4f6f314b06b04f139394] Marking url as dead. Last error: [LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError] Elasticsearch Unreachable: [http://elastic:xxxxxx@server_name:9200/][Manticore::SocketTimeout] Read timed out {:url=>http://elastic:xxxxxx@server_name:9200/, :error_message=>"Elasticsearch Unreachable: [http://elastic:xxxxxx@server_name:9200/][Manticore::SocketTimeout] Read timed out", :error_class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError"}
[2020-10-28T11:31:26,846][ERROR][logstash.outputs.elasticsearch][main][93fecca09435a6ec0a5624ad0c9131d67dd7f680e35db24c6150de34cfa21d51] Attempted to send a bulk request to elasticsearch' but Elasticsearch appears to be unreachable or down! {:error_message=>"Elasticsearch Unreachable: [http://elastic:xxxxxx@server_name:9200/][Manticore::SocketTimeout] Read timed out", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError", :will_retry_in_seconds=>2}

```

My logstash configuration looks like :

```auto
output {
           elasticsearch {
                hosts => "${ES_SERVER}
                index => "%{index_name}"
                pipeline => enrichment_pipeline_name
                user => "${ES_USER}"
                password => "${ES_PASS}"
                }
}

```

I found below article suggeting to reduce the worker but I am using default setting. not specifying any worker setting in my job.

> **[Tuning Logstash as Elastic Search becomes Not Reachable](https://medium.com/@rkgurram/tuning-logstash-as-elastic-search-becomes-not-reachable-bd2365850714)**
>
> Introduction

---

<div class="post-metadata">

**Author:** ![Vijay\_Barai](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vijay_barai/32/76087_2.png) [@Vijay\_Barai](https://discuss.elastic.co/u/Vijay_Barai)\
**Post date:** [October 28, 2020, 4:18pm UTC](https://discuss.elastic.co/t/ingest-node-pipelines-making-elasticsearch-unreachable/253534/2 "2020-10-28T16:18:33Z")

</div>

Hi All,  
I am able to resolved this issue. I was using a pipeline like below causing this error:

```auto
 Main_Pipeline -> Pipeline_1
               |-> Pipeline_2
               |-> Pipeline_3
               |-> Script
               |-> Remove

```

When I changed it to below it resolved the issue

```auto
Main_Pipeline --> Pipeline_1
              |-> Pipeline_2
              |-> Pipeline_3
              |-> Pipeline_4 --> Script
                             |-> Remove

```

---

<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:** [November 25, 2020, 4:18pm UTC](https://discuss.elastic.co/t/ingest-node-pipelines-making-elasticsearch-unreachable/253534/3 "2020-11-25T16:18:34Z")

</div>

Closed on November 25, 2020, 4:18pm UTC

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