# Corruption of Elasticsearch indices

**URL:** <https://discuss.elastic.co/t/corruption-of-elasticsearch-indices/65475>\
**Category:** Elasticsearch\
**Created:** [November 9, 2016, 11:39am UTC](https://discuss.elastic.co/t/corruption-of-elasticsearch-indices/65475 "2016-11-09T11:39:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexsch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexsch/32/13056_2.png) [@alexsch](https://discuss.elastic.co/u/alexsch)\
**Post date:** [November 9, 2016, 11:39am UTC](https://discuss.elastic.co/t/corruption-of-elasticsearch-indices/65475/1 "2016-11-09T11:39:42Z")

</div>

Does somebody know if we can have a scenario where a physical disk can become corrupted, while the in-memory Elasticsearch indices data is fine?

In this case, how can we trigger Elasticsearch to synchronize with the disk at some specified time interval?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [November 13, 2016, 8:16am UTC](https://discuss.elastic.co/t/corruption-of-elasticsearch-indices/65475/2 "2016-11-13T08:16:29Z")

</div>

There's no in memory index, so there's no way.

---

<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:** [December 11, 2016, 8:17am UTC](https://discuss.elastic.co/t/corruption-of-elasticsearch-indices/65475/3 "2016-12-11T08:17:09Z")

</div>

Closed on December 11, 2016, 8:17am UTC

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