- Restart Elastic Search, any one index get following error and ES
Indices were not opened, after the error indices deletion, cluster
will come green and it’s working fine. So every ES restart we loss any
one indices.
We are using Elastic search version 16.0
“[01:48:56,425][WARN ][cluster.action.shard ] [O'Sullivan,
Solomon] sending f
ailed shard for [db288_audit][2], node[SoJVrnNpSsy7uDEA3qRnBw], [P],
s[INITIALIZ
ING], reason [Failed to start shard, message
[IndexShardGatewayRecoveryException
[[db288_audit][2] No commit point data is available in gateway]]]
[01:48:56,582][WARN ][index.gateway.fs ] [O'Sullivan, Solomon]
[db288_au
dit][2] failed to read commit point [commit-1]
java.lang.ArrayIndexOutOfBoundsException
[01:48:56,582][WARN ][index.gateway.fs ] [O'Sullivan, Solomon]
[db288_au
dit][2] listed commit_point [commit-0]/[0], but not all files exists,
ignoring
[01:48:56,582][WARN ][indices.cluster ] [O'Sullivan, Solomon]
[db288_au
dit][2] failed to start shard
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException:
[db288_audit
][2] No commit point data is available in gateway
at
org.elasticsearch.index.gateway.blobstore.BlobStoreIndexShardGateway.
recover(BlobStoreIndexShardGateway.java:423)
at org.elasticsearch.index.gateway.IndexShardGatewayService
$1.run(IndexS
hardGatewayService.java:144)
at java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExec
utor.java:886)
at java.util.concurrent.ThreadPoolExecutor
$Worker.run(ThreadPoolExecutor
.java:908)
at java.lang.Thread.run(Thread.java:619)”
What's going wrong here....?
Can any one help me...