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.
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.
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.
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.
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 daaqou@gmail.com 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.
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.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.