I have had such a problem with a few shards. The allocation fails with the following message:
RecoveryFailedException: Recovery failed from X into Y; nested: RemoteTransportException Y; nested: RecoveryEngineException ... Phase[2] Execution failed; nested: RemoteTransportException ...[index/shard/recovery/translogOps]]; nested: MapperParsingException[failed to parse [...]]; nested: ElasticsearchIllegalArgumentException[unknown property [foo]]; ]] In this case it seems dynamic-mapping for property foo wasn't propagated to all shards, now a few shards that somehow don't know the mapping for foo are not able to initialize on any node. I need to find out why the mapping for field foo is unknown though. Doesn't log tell you why its not able to initialize the shard? On Mon, Jan 19, 2015 at 8:51 PM, daaku gee <[email protected]> wrote: > By bouncing I mean the shard sits on one node for a little less than a > minute then moves over to a second node, then back to the first node after > a few seconds. It stays in INITIALIZING state. > > On Mon, Jan 19, 2015 at 5:26 PM, Mark Walkom <[email protected]> wrote: > >> Bouncing? Does it allocate or just sit in a allocating state? >> >> On 20 January 2015 at 00:06, daaku gee <[email protected]> wrote: >> >>> I am running 3 node Elasticsearch-1.3 cluster. One of the primary >>> shards for an index that has no more documents being indexed to it, keeps >>> bouncing from node to node. No its not relocating. >>> >>> Allocating the shard to any one node doesn't work. >>> >>> What can I do to stabilize it? >>> >>> Thanks >>> >>> -- >>> 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/CAH53p94GkK2iw3m4-4UKTv8JPORD6k%2B7DZ1jLYrfgT7LqX_20g%40mail.gmail.com >>> <https://groups.google.com/d/msgid/elasticsearch/CAH53p94GkK2iw3m4-4UKTv8JPORD6k%2B7DZ1jLYrfgT7LqX_20g%40mail.gmail.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 [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ntBtgGMfM2YFx7wgUSdydjTW-s4XD5wxv-9af%3DkAA2g%40mail.gmail.com >> <https://groups.google.com/d/msgid/elasticsearch/CAEYi1X_ntBtgGMfM2YFx7wgUSdydjTW-s4XD5wxv-9af%3DkAA2g%40mail.gmail.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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elasticsearch/CAH53p94mMXv5jMcE_wKuVfKzrkkX6LsFG%2BAyXaK41R3T%2Bry6Gw%40mail.gmail.com > <https://groups.google.com/d/msgid/elasticsearch/CAH53p94mMXv5jMcE_wKuVfKzrkkX6LsFG%2BAyXaK41R3T%2Bry6Gw%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Regards, Janmejay http://codehunk.wordpress.com -- 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/CAGB1VvwCjggJCwXuUo9R48ffuaMrxr297iRUMpm6Fm1eqHDSow%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
