# Elasticsearch (sort of) losing pipelines on restart

**URL:** <https://discuss.elastic.co/t/elasticsearch-sort-of-losing-pipelines-on-restart/88688>\
**Category:** Elasticsearch\
**Created:** [June 8, 2017, 8:48am UTC](https://discuss.elastic.co/t/elasticsearch-sort-of-losing-pipelines-on-restart/88688 "2017-06-08T08:48:08Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![meerlicht](https://avatars.discourse-cdn.com/v4/letter/m/a88e4f/32.png) [@meerlicht](https://discuss.elastic.co/u/meerlicht)\
**Post date:** [June 18, 2017, 8:25pm UTC](https://discuss.elastic.co/t/elasticsearch-sort-of-losing-pipelines-on-restart/88688/6 "2017-06-18T20:25:02Z")

</div>

I'm still trying to understand and made some progress:

- Cluster is setup from scratch; all is fine
- If adding all my pipelines, then restarting elasticsearch I'm back to the error:

`java.lang.IllegalArgumentException: pipeline with id [xpack_monitoring_2] does not exist`

but yet it's there:

> curl -XGET 'localhost:9200/\_ingest/pipeline/xpack\_monitoring\_2?pretty'  
> {  
> "xpack\_monitoring\_2" : {  
> "description" : "2: This is a placeholder pipeline for Monitoring API version 2 so that future versions may fix breaking changes.",  
> "processors" :   
> }  
> }

So: I've started to add my pipelines one by one and found that the error starts as soon as I'm adding a pipeline with a painless-script. Adding the pipeline with the painless-script renders all my pipelines unusable after a restart of the Elasticsearch server ingest node until I delete and re-add all pipelines to the running Elasticsearch server.

I'll try to simplify my setup to then post a sample script & pipeline here.

Additionally this might be related to these topics:

> [@\[Ingest Node\] pipeline with id \[x\] does not exist](https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist/84570):
>
> I think this is the same problem noted here: [https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436](https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436) That thread says "solved" but I see no resolution. Just an inability to reproduce the error. We're still getting the error in later versions. Details: ES 5.1.1 Using 2 custom processors Single node cluster(s) Has occurred in at least half a dozen clusters I don't think I could do a better job at noting the specifics than @PatrickKik so I'll quote him:

> [@\[Ingest Node\] pipeline with id \[x\] does not exist (solved)](https://discuss.elastic.co/t/ingest-node-pipeline-with-id-x-does-not-exist-solved/54436):
>
> SOLVED Just minutes before the release of 5.0.0-alpha4 I found this bug. I tried it in `5.0.0-alpha4' and it works fine. That's nice. But it still feels like I have lost some time... weary I'm using elasticsearch-5.0.0-alpha3 and kibana-5.0.0-alpha3. Using Console I register a pipeline: PUT \_ingest/pipeline/x { "description": "Ingesting Meetup events", "processors": [...] } When I check if my pipeline exists: GET \_ingest/pipeline/x It comes back the way it should: { "pipeline…

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-sort-of-losing-pipelines-on-restart/88688)._