Could not initialize the shard


(Илья Четверкин) #1

Hey!

I have a problem with one shard in my index:

"7" : [ {
"state" : "INITIALIZING",
"primary" : true,
"node" : "cphuCdBbTPKfa1hlcCLGVg",
"relocating_node" : null,
"shard" : 7,
"index" : "vkontakte"
}, {
"state" : "UNASSIGNED",
"primary" : false,
"node" : null,
"relocating_node" : null,
"shard" : 7,
"index" : "vkontakte"
} ],

It could not initialize and replica remains unassigned all the time. Thus i have red status of all the cluster.

Digging the logs i've found that it is the lock issue:

[2014-02-20 07:44:59,918][WARN ][cluster.action.shard ] [Big Man] [vkontakte][7] sending failed shard for [vkontakte][7], node[WMpyEC4iRGuSOsGjSlB-Yw], [P], s[INITIALIZING], indexUUID [SpXdJVZWTCqRJlKXMKFi-g], reason [Failed to start shard, message [IndexShardGatewayRecoveryException[[vkontakte][7] failed recovery]; nested: EngineCreationFailureException[[vkontakte][7] failed to create engine]; nested: LockReleaseFailedException[Cannot forcefully unlock a NativeFSLock which is held by another indexer component: /var/lib/elasticsearch/elasticsearch/nodes/0/indices/vkontakte/7/index/write.lock]; ]]

But if I stop the node and remove write.lock it become available until the indexing started.

Any suggestions how to fix this issue?

(ES version 0.90.10)

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e9dbb815-a8bf-4fc2-9422-b0dc2b850f91%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


(system) #2