# How to prevent shard data loss during ES shutdown

**URL:** <https://discuss.elastic.co/t/how-to-prevent-shard-data-loss-during-es-shutdown/81583>\
**Category:** Elasticsearch\
**Created:** [April 7, 2017, 8:17am UTC](https://discuss.elastic.co/t/how-to-prevent-shard-data-loss-during-es-shutdown/81583 "2017-04-07T08:17:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ABChocolate](https://avatars.discourse-cdn.com/v4/letter/a/c77e96/32.png) [@ABChocolate](https://discuss.elastic.co/u/ABChocolate)\
**Post date:** [April 7, 2017, 8:17am UTC](https://discuss.elastic.co/t/how-to-prevent-shard-data-loss-during-es-shutdown/81583/1 "2017-04-07T08:17:20Z")

</div>

Hi,

During shutdown due to ES settings or version patches,  
how can I prevent the loss of shard data that is piled up?

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 7, 2017, 9:36am UTC](https://discuss.elastic.co/t/how-to-prevent-shard-data-loss-during-es-shutdown/81583/2 "2017-04-07T09:36:12Z")

</div>

If you have a cluster, do a rolling upgrade.

Or use a pipeline which keeps event until they are delivered to elasticsearch.

Logstash. Or logstash + Kafka for example.

---

<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:** [May 5, 2017, 9:45am UTC](https://discuss.elastic.co/t/how-to-prevent-shard-data-loss-during-es-shutdown/81583/3 "2017-05-05T09:45:24Z")

</div>

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