ES Error - No commit point data is available in gateway

senthil_prabhu · May 28, 2011, 4:54am

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...

kimchy · May 28, 2011, 9:18am

Can you please gist the exception. Which shared gateway are you using?

On Saturday, May 28, 2011 at 7:54 AM, senthil prabhu wrote:

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...

senthil_prabhu · May 28, 2011, 11:30am

We are using FS shared gateway and the Exception i am getting is

“[01:48:56,425][WARN ][cluster.action.shard ] [O'Sullivan,
Solomon] sending failed 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_audit][2] failed to read commit point
[commit-1]java.lang.ArrayIndexOutOfBoundsException
[01:48:56,582][WARN ][index.gateway.fs] [O'Sullivan, Solomon]
[db288_audit][2] listed commit_point [commit-0]/[0], but not all files
exists, ignoring
[01:48:56,582][WARN ][indices.cluster] [O'Sullivan, Solomon]
[db288_audit][2] failed to start
shardorg.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(IndexShardGatewayService.java:144) at
java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) at java.lang.Thread.run(Thread.java:619)”

On May 28, 2:18 pm, Shay Banon shay.ba...@elasticsearch.com wrote:

Can you please gist the exception. Which shared gateway are you using?

On Saturday, May 28, 2011 at 7:54 AM, senthil prabhu wrote:

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...

kimchy · May 28, 2011, 1:47pm

Can you GIST (http://gist.github.com) the full log of the node where you see this exception?

On Saturday, May 28, 2011 at 2:30 PM, senthil prabhu wrote:

We are using FS shared gateway and the Exception i am getting is

“[01:48:56,425][WARN ][cluster.action.shard ] [O'Sullivan,
Solomon] sending failed 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_audit][2] failed to read commit point
[commit-1]java.lang.ArrayIndexOutOfBoundsException
[01:48:56,582][WARN ][index.gateway.fs] [O'Sullivan, Solomon]
[db288_audit][2] listed commit_point [commit-0]/[0], but not all files
exists, ignoring
[01:48:56,582][WARN ][indices.cluster] [O'Sullivan, Solomon]
[db288_audit][2] failed to start
shardorg.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(IndexShardGatewayService.java:144) at
java.util.concurrent.ThreadPoolExecutor
$Worker.runTask(ThreadPoolExecutor.java:886) at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor
.java:908) at java.lang.Thread.run(Thread.java:619)”

On May 28, 2:18 pm, Shay Banon <shay.ba...@elasticsearch.com (http://elasticsearch.com)> wrote:

Can you please gist the exception. Which shared gateway are you using?

On Saturday, May 28, 2011 at 7:54 AM, senthil prabhu wrote:

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...

fashionalwallet · June 10, 2011, 3:43am

deleted -

Topic		Replies	Views
ES index gateway issues Elasticsearch	2	271	July 6, 2017
No commit point data is available in gateway Elasticsearch	13	362	July 6, 2017
No commit point data in gateway Elasticsearch	1	255	July 6, 2017
ES Cluster Restart Issue Elasticsearch	4	322	July 6, 2017
Problem when restart ES Elasticsearch	6	307	July 6, 2017

ES Error - No commit point data is available in gateway

Related topics