determination elasticsearch recovery failure
up vote
0
down vote
favorite
I was wondering how to determine the failure of a snapshot recovery.
From the Elasticsearch documentation, cat-recovery can be used to determine if an index or indices are being recovered from some source.
Per recovering shard, the stage, one of init, index, start, translog, finalize, done , tells how far along in the process recovery it’s in.
In the case that for whatever reason recovery fails, would the stage come to rest at whatever stage failure occurred on? Or will stage of the failed shard transition to “done” and we can then determine failure of the recovery based on the color coded health status of said shard?
Perhaps there’s a “failure” value that I’ve missed somewhere?
Thanks!
elasticsearch
add a comment |
up vote
0
down vote
favorite
I was wondering how to determine the failure of a snapshot recovery.
From the Elasticsearch documentation, cat-recovery can be used to determine if an index or indices are being recovered from some source.
Per recovering shard, the stage, one of init, index, start, translog, finalize, done , tells how far along in the process recovery it’s in.
In the case that for whatever reason recovery fails, would the stage come to rest at whatever stage failure occurred on? Or will stage of the failed shard transition to “done” and we can then determine failure of the recovery based on the color coded health status of said shard?
Perhaps there’s a “failure” value that I’ve missed somewhere?
Thanks!
elasticsearch
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I was wondering how to determine the failure of a snapshot recovery.
From the Elasticsearch documentation, cat-recovery can be used to determine if an index or indices are being recovered from some source.
Per recovering shard, the stage, one of init, index, start, translog, finalize, done , tells how far along in the process recovery it’s in.
In the case that for whatever reason recovery fails, would the stage come to rest at whatever stage failure occurred on? Or will stage of the failed shard transition to “done” and we can then determine failure of the recovery based on the color coded health status of said shard?
Perhaps there’s a “failure” value that I’ve missed somewhere?
Thanks!
elasticsearch
I was wondering how to determine the failure of a snapshot recovery.
From the Elasticsearch documentation, cat-recovery can be used to determine if an index or indices are being recovered from some source.
Per recovering shard, the stage, one of init, index, start, translog, finalize, done , tells how far along in the process recovery it’s in.
In the case that for whatever reason recovery fails, would the stage come to rest at whatever stage failure occurred on? Or will stage of the failed shard transition to “done” and we can then determine failure of the recovery based on the color coded health status of said shard?
Perhaps there’s a “failure” value that I’ve missed somewhere?
Thanks!
elasticsearch
elasticsearch
asked Nov 9 at 23:30
maoshouse
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
_cat/recovery is not for snapshot recovery statue. for snapshot restore failure you can get the statue as below:
curl XGET "127.0.0.1:9200/_snapshot/my_backup/snapshot_1"
my_backup
is the name of repository and
snapshot_1
is the name of snapshot you have created.
the result have these parameters:
IN_PROGRESS
The snapshot is currently running.
SUCCESS
The snapshot finished and all shards were stored successfully.
FAILED
The snapshot finished with an error and failed to store any data.
PARTIAL
The global cluster state was stored, but data of at least one shard wasn’t stored successfully. The failure section in this case should contain more detailed information about shards that were not processed correctly.
INCOMPATIBLE
The snapshot was created with an old version of Elasticsearch and therefore is incompatible with the current version of the cluster.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
_cat/recovery is not for snapshot recovery statue. for snapshot restore failure you can get the statue as below:
curl XGET "127.0.0.1:9200/_snapshot/my_backup/snapshot_1"
my_backup
is the name of repository and
snapshot_1
is the name of snapshot you have created.
the result have these parameters:
IN_PROGRESS
The snapshot is currently running.
SUCCESS
The snapshot finished and all shards were stored successfully.
FAILED
The snapshot finished with an error and failed to store any data.
PARTIAL
The global cluster state was stored, but data of at least one shard wasn’t stored successfully. The failure section in this case should contain more detailed information about shards that were not processed correctly.
INCOMPATIBLE
The snapshot was created with an old version of Elasticsearch and therefore is incompatible with the current version of the cluster.
add a comment |
up vote
0
down vote
_cat/recovery is not for snapshot recovery statue. for snapshot restore failure you can get the statue as below:
curl XGET "127.0.0.1:9200/_snapshot/my_backup/snapshot_1"
my_backup
is the name of repository and
snapshot_1
is the name of snapshot you have created.
the result have these parameters:
IN_PROGRESS
The snapshot is currently running.
SUCCESS
The snapshot finished and all shards were stored successfully.
FAILED
The snapshot finished with an error and failed to store any data.
PARTIAL
The global cluster state was stored, but data of at least one shard wasn’t stored successfully. The failure section in this case should contain more detailed information about shards that were not processed correctly.
INCOMPATIBLE
The snapshot was created with an old version of Elasticsearch and therefore is incompatible with the current version of the cluster.
add a comment |
up vote
0
down vote
up vote
0
down vote
_cat/recovery is not for snapshot recovery statue. for snapshot restore failure you can get the statue as below:
curl XGET "127.0.0.1:9200/_snapshot/my_backup/snapshot_1"
my_backup
is the name of repository and
snapshot_1
is the name of snapshot you have created.
the result have these parameters:
IN_PROGRESS
The snapshot is currently running.
SUCCESS
The snapshot finished and all shards were stored successfully.
FAILED
The snapshot finished with an error and failed to store any data.
PARTIAL
The global cluster state was stored, but data of at least one shard wasn’t stored successfully. The failure section in this case should contain more detailed information about shards that were not processed correctly.
INCOMPATIBLE
The snapshot was created with an old version of Elasticsearch and therefore is incompatible with the current version of the cluster.
_cat/recovery is not for snapshot recovery statue. for snapshot restore failure you can get the statue as below:
curl XGET "127.0.0.1:9200/_snapshot/my_backup/snapshot_1"
my_backup
is the name of repository and
snapshot_1
is the name of snapshot you have created.
the result have these parameters:
IN_PROGRESS
The snapshot is currently running.
SUCCESS
The snapshot finished and all shards were stored successfully.
FAILED
The snapshot finished with an error and failed to store any data.
PARTIAL
The global cluster state was stored, but data of at least one shard wasn’t stored successfully. The failure section in this case should contain more detailed information about shards that were not processed correctly.
INCOMPATIBLE
The snapshot was created with an old version of Elasticsearch and therefore is incompatible with the current version of the cluster.
answered Nov 10 at 7:04
hamid bayat
387
387
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53234565%2fdetermination-elasticsearch-recovery-failure%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown