# Shard merge seems to fail **URL:** \ **Category:** Elasticsearch\ **Created:** [October 8, 2014, 9:08am UTC](https://discuss.elastic.co/t/shard-merge-seems-to-fail/20133 "2014-10-08T09:08:35Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Daniel\_Alonso\_Heras](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@Daniel\_Alonso\_Heras](https://discuss.elastic.co/u/Daniel_Alonso_Heras)\ **Post date:** [October 8, 2014, 9:08am UTC](https://discuss.elastic.co/t/shard-merge-seems-to-fail/20133/1 "2014-10-08T09:08:35Z")
Hi all, I'm using elasticsearch 1.2.1 with java 1.7.0\_60. I have one index with 52 shards and 1 replica in three servers. Till yesterday all was working like a charm, but yesterday we started facing an strange issue. After every inserts/updates by bulk load one of the primary shards (allways is the same one) while merging process keep growing (upto 1GB more than the normal size) and after that this primary shard is removed from that node and started in a different one (also the replica is moved) with the normal size. At this moment this is not causing any data corruption but this is very strange for us as while reallocating the primary it is sometimes in red state (just for milliseconds). In elasticsearch logs (INFO level) there is nothing at all. Could someone help me with this issue? Thanks in advance -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5700b41e-e4ad-40a8-a361-9d2be85b6517%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5700b41e-e4ad-40a8-a361-9d2be85b6517%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Daniel\_Alonso\_Heras](https://avatars.discourse-cdn.com/v4/letter/d/bc79bd/32.png) [@Daniel\_Alonso\_Heras](https://discuss.elastic.co/u/Daniel_Alonso_Heras)\ **Post date:** [October 9, 2014, 1:15pm UTC](https://discuss.elastic.co/t/shard-merge-seems-to-fail/20133/2 "2014-10-09T13:15:23Z")
I have seen with lucene CheckIndex tool that the shard that is failing is corrupt.... How could it have happened? and, how could it be fixed? El miércoles, 8 de octubre de 2014 11:08:35 UTC+2, Daniel Alonso Heras escribió: > Hi all, > > I'm using elasticsearch 1.2.1 with java 1.7.0\_60. I have one index with 52 > shards and 1 replica in three servers. Till yesterday all was working like > a charm, but yesterday we started facing an strange issue. > > After every inserts/updates by bulk load one of the primary shards > (allways is the same one) while merging process keep growing (upto 1GB more > than the normal size) and after that this primary shard is removed from > that node and started in a different one (also the replica is moved) with > the normal size. > > At this moment this is not causing any data corruption but this is very > strange for us as while reallocating the primary it is sometimes in red > state (just for milliseconds). > > In elasticsearch logs (INFO level) there is nothing at all. > > Could someone help me with this issue? > > Thanks in advance -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8ac0e804-391d-4838-a652-79a045d8b91a%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ac0e804-391d-4838-a652-79a045d8b91a%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:57am UTC](https://discuss.elastic.co/t/shard-merge-seems-to-fail/20133/3 "2017-07-06T00:57:19Z")