I have the error (503), No Shard Available Action Exception

Elastic Stack Elasticsearch
1 
"version" : {
    "number" : "2.3.0",
    "build_hash" : "8371be8d5fe5df7fb9c0516c474d77b9feddd888",
    "build_timestamp" : "2016-03-29T07:54:48Z",
    "build_snapshot" : false,
    "lucene_version" : "5.5.0"
  }

When I have opened some old closed index, I got error no_shard_available_action_exception.

curl -XGET localhost:9200/prd-2016.04/allocation/explain?pretty
{
  "error" : {
    "root_cause" : [ {
      "type" : "no_shard_available_action_exception",
      "reason" : "No shard available for [get [prd-2016.04][allocation][explain]: routing [null]]"
    } ],
    "type" : "no_shard_available_action_exception",
    "reason" : "No shard available for [get [prd-2016.04][allocation][explain]: routing [null]]"
  },
  "status" : 503
}

curl -XGET localhost:9200/_cat/shards?h=index,shard,prirep,state,unassigned.reason| grep UNASSIGNED    
prd-2016.04          1 p UNASSIGNED INDEX_REOPENED
prd-2016.04          1 r UNASSIGNED INDEX_REOPENED
prd-2016.04          2 p UNASSIGNED INDEX_REOPENED
prd-2016.04          2 r UNASSIGNED INDEX_REOPENED
prd-2016.04          4 p UNASSIGNED INDEX_REOPENED
prd-2016.04          4 r UNASSIGNED INDEX_REOPENED
prd-2016.04          3 p UNASSIGNED INDEX_REOPENED
prd-2016.04          3 r UNASSIGNED INDEX_REOPENED
prd-2016.04          0 p UNASSIGNED INDEX_REOPENED
prd-2016.04          0 r UNASSIGNED INDEX_REOPENED

Is it possible to restore a closed index?
Thanks in advance.

2

May be you had nodes that have been killed in the meantime, including ones which had the primary shards?

If it's the case and you don't have those nodes again and no snapshot (backup), I'm afraid you won't be able to get your data back online.

3

I guess your clusters have been unexpected shutdown one or two times.
Thank you your reply.

4

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.