# Elasticsearch index corruption?

**URL:** <https://discuss.elastic.co/t/elasticsearch-index-corruption/138002>\
**Category:** Elasticsearch\
**Created:** [June 29, 2018, 3:56pm UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002 "2018-06-29T15:56:47Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ramon\_Zaro](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@Ramon\_Zaro](https://discuss.elastic.co/u/Ramon_Zaro)\
**Post date:** [June 29, 2018, 3:56pm UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002/1 "2018-06-29T15:56:47Z")

</div>

Hi, I am running a ES 6.3 on a single node fed by fscrawler 2.4 on a fileshare. It was working fine for few days but suddenly there was an issue that certain keywords would give a timeout (searched using kibana 6.3) or a no response (.NET client using ES6.3 rest service).

I am really perplexed as to the cause, the node has 40 shards of which 5 are unallocated, thus health is showing yellow.

My questions are :  
a) has the index been corrupted? is there a way to check that ?  
b) if so, can it be recovered ?  
c) what are the reasons that can lead to such corruption of index and how to avoid them?

thanks in advance.

---

<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:** [June 30, 2018, 6:59am UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002/2 "2018-06-30T06:59:46Z")

</div>

It'd be best if you have a look in your Elasticsearch logs before jumping at corruption concerns.  
Can you find them and post a few excerpts?

---

<div class="post-metadata">

**Author:** ![Ramon\_Zaro](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@Ramon\_Zaro](https://discuss.elastic.co/u/Ramon_Zaro)\
**Post date:** [July 2, 2018, 6:03pm UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002/3 "2018-07-02T18:03:33Z")

</div>

Hi @warkolm, I did have a look at the logs and they frankly didn't have anything of note.

Other than some g.c messages there was absolutely nothing. slowlogs were empty.

Please let me know if there's something else I can have a look at to gauge what's going on.

Currently, some keywords return a result while others timeout; f.e 'vanderbilt' times out, while 'van' & 'van\*' returns results.

---

<div class="post-metadata">

**Author:** ![Ramon\_Zaro](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@Ramon\_Zaro](https://discuss.elastic.co/u/Ramon_Zaro)\
**Post date:** [July 8, 2018, 8:54am UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002/4 "2018-07-08T08:54:00Z")

</div>

@warkolm, anyone ? anything ?

I saw a few issues reported with G.C, does that have anything to do with this ?

---

<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:** [July 8, 2018, 8:55am UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002/5 "2018-07-08T08:55:23Z")

</div>

Perhaps if you show your query.

---

<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:** [August 5, 2018, 9:08am UTC](https://discuss.elastic.co/t/elasticsearch-index-corruption/138002/6 "2018-08-05T09:08:31Z")

</div>

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