I have two Elasticsearch nodes on server A and B .Each node is storing the
indices on two SANs (Storage area network) mounted on each server.
I booted up another server C with a single elastic search node on it. And
then, unmounted one of the SAN on the server A and mounted it on server C.
I restarted the whole cluster again with the new placement of the SANs. I
assumed that the cluster will find the manually moved shards and it will
initialize them accordingly . But this isn't the case. I am getting the
below warning messages in the logs.
sending failed shard for [2013-12-26.06:00], node[VD7c5WgxSaaTZ2_6yRgcLQ
], [P], s[INITIALIZING], reason [Failed to start shard, message [
IndexShardGatewayRecoveryException[[2013-12-26.06:00] shard allocated for
local recovery (post api), should exist, but doesn't, current files:[......
The above warn message is pretty straightforward. It just means that the
local recovery for a particular index failed due to SAN relocation, which
But I want the cluster to search for the shards on other nodes too. But
somehow the moved shards are not getting located by the cluster.
Is there a way to initialize these manually moved shards correctly?
Also, can anyone elaborate on what meta information that is stored in the
Elasticsearch index which is used by the local node and also the whole
cluster during recovery ?
Oh , btw I am using Elasticsearch version - 0.90.5
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@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/cfccfc5a-6521-4a39-8d28-201daa5b7484%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.