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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8ac0e804-391d-4838-a652-79a045d8b91a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
