I have error 503, No Shard Available Action Exception with Elasticsearch

I am having problems when I search for a register inside an index and the following message is:

TransportError: TransportError(503, u'NoShardAvailableActionException[[new_gompute_history][2] null]; nested: IllegalIndexShardStateException[[new_gompute_history][2] CurrentState[POST_RECOVERY] operations only allowed when started/relocated]; ')

      

This happens when I loop through the ID inside the index.

My cluster health is green:

GET _cat/health?v

epoch      timestamp cluster status node.total node.data shards pri relo init unassign 
1438678496 10:54:56  juan    green           5         4    212 106    0    0        0 


GET _cat/allocation?v

shards disk.used disk.avail disk.total disk.percent host    ip         node                   
    53     3.1gb     16.8gb       20gb           15 bc10-05 10.8.5.15  Anomaloco              
    53     6.4gb     80.8gb     87.3gb            7 bc10-03 10.8.5.13  Algrim the Strong      
     0        0b                                    l8a     10.8.0.231 logstash-l8a-5920-4018 
    53     6.4gb     80.8gb     87.3gb            7 bc10-03 10.8.5.13  Harry Leland           
    53     3.1gb     16.8gb       20gb           15 bc10-05 10.8.5.15  Hypnotia

      

I decided to put sleep time between consecutive PUTs, but I don't like this solution

+3
elasticsearch sharding


source to share


No one has answered this question yet

See similar questions:

1
org.elasticsearch.action.NoShardAvailableActionException in elasticsearch

or similar:

265
Shards and replicas in Elasticsearch
147
ElasticSearch: Unallocated shards, how to fix it?
7
Elasticearch cluster leaving shards unassigned
2
ElasticSearch Unallocated shards with two nodes (different machines), 1 master and new instances
1
Redistributing Elasticsearch turtles
1
Elasticsearch Cluster Health Yellow
0
Unallocated index shards in ElasticSearch
0
Elastic detectors thickened fragments?
0
Upgrading from 5.2.2 to 6.4.2 (yum install VS yum update)
0
elasticsearch in docker cluster name is the same but not clustered



All Articles
Loading...
X
Show
Funny
Dev
Pics