# Lost Pipelines after ES restart

**URL:** <https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481>\
**Category:** Elasticsearch\
**Created:** [August 8, 2018, 10:07am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481 "2018-08-08T10:07:54Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![brais](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@brais](https://discuss.elastic.co/u/brais)\
**Post date:** [August 8, 2018, 10:07am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/1 "2018-08-08T10:07:54Z")

</div>

Everytime we restart our cluster, we lose all the pipelines. So we have to push them everytime we start it again. And we should do that everyday as we power off our kubermetes cluster every night.  
We have two kubernetes deployments (prod,staging) using github pires images (version 6.2.2). We are suffering this behaviour on both clusters.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 8, 2018, 10:44am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/2 "2018-08-08T10:44:09Z")

</div>

Are you nodes configured to use persistent storage?

---

<div class="post-metadata">

**Author:** ![brais](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@brais](https://discuss.elastic.co/u/brais)\
**Post date:** [August 8, 2018, 11:01am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/3 "2018-08-08T11:01:30Z")

</div>

Hi,

Data nodes are using persistent storage, we don't lose the data between reboots, but master and client nodes aren't...

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [August 8, 2018, 11:03am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/4 "2018-08-08T11:03:06Z")

</div>

Master nodes also need persistent storage.

---

<div class="post-metadata">

**Author:** ![brais](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@brais](https://discuss.elastic.co/u/brais)\
**Post date:** [August 8, 2018, 11:05am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/5 "2018-08-08T11:05:05Z")

</div>

So, they are storing pipeline and cluster info?  
By the way, which folders should persist between reboots?

---

<div class="post-metadata">

**Author:** ![brais](https://avatars.discourse-cdn.com/v4/letter/b/85e7bf/32.png) [@brais](https://discuss.elastic.co/u/brais)\
**Post date:** [August 9, 2018, 6:39am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/6 "2018-08-09T06:39:23Z")

</div>

Now I could answer my own questions...  
It looks like pipeline data is stored in the master nodes, the folder that should be made persistent between reboots is /data as in the data nodes.

Thanks for your help

---

<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 6, 2018, 6:39am UTC](https://discuss.elastic.co/t/lost-pipelines-after-es-restart/143481/7 "2018-09-06T06:39:28Z")

</div>

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