Noticed this happening on a cluster this week which had reached 85%, the full disk watermark.
On Thursday, April 2, 2015 at 3:29:18 PM UTC-6, Mark Walkom wrote: > > Take a look in your ES logs, it should have something of use. > > You can also try dropping the replicas to 0 for the indices that are > having these problems, then readd them one index at a time. > > On 2 April 2015 at 23:42, Darius <dari...@gmail.com <javascript:>> wrote: > >> Hello, >> >> Quick description of the problem: I had 1 elasticsearch server cluster >> with 0 replicas for all indexes, then added a second ES server to the >> cluster and then set that all existing indexes should have 1 replica >> (instead of the 0) . >> After doing this, in the _cat/shards page I could see that it created >> twice as many indexes/indexes(?) (sorry, im not that good with the ES >> terminology) and all the new ones were UNASSIGNED. They then started >> slowly INITIALIZING (2 at a time) and then go to STARTED state on the >> second server. So thats good, but the problem is that this was done like 2 >> weeks ago and some of them are still UNASSIGNED or INITIALIZING. I've even >> noticed some of them going into the INITIALIZING state and then falling >> back to UNASSIGNED. How can I properly find the problem here and is there >> any way I can force the replicas to be allocated to the 2nd node WITHOUT >> any data loss? I found only one way to allocate, but that includes data >> loss, unfortunately. >> >> I don't have tons of data in there so I dont see why it should take so >> long. The largest index is ±500M in size, most of them are a few megs and >> the total number is around ±150-200. >> >> any help would be appreciated.. >> >> -- >> 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 elasticsearc...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/05cad3e5-78ce-44f7-9a30-6ca0eb817237%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/05cad3e5-78ce-44f7-9a30-6ca0eb817237%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/fb5aeaaa-f3ea-4d3c-af96-9b7eb0676ab5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
