no_shard_available_action_exception: no_shard_available_action_exception: No shard available for [...]
ElasticsearchWhat does it mean?
No active shard copy capable of serving a request was found. The request cannot be fulfilled because the relevant shard is unassigned, recovering, or its hosting node is unreachable.
Why does it happen?
A node crash/network partition, unassigned shards, an ongoing shard recovery, an allocation block due to the disk watermark, or the cluster being in the RED/YELLOW state.
How to fix it
Inspect cluster and shard state: GET _cluster/health and GET _cat/shards?v. See why shards are unassigned: GET _cluster/allocation/explain. Bring crashed nodes back, fix the disk problem, and wait for recovery to finish: GET _cat/recovery?v&active_only=true. If needed, retry allocation with POST _cluster/reroute?retry_failed=true.
More from this engine
- index_not_found_exceptionindex_not_found_exception: no such index [index_name] (HTTP 404)
- resource_already_exists_exceptionresource_already_exists_exception: index [index_name/uuid] already exists (HTTP 400)
- cluster_health_redcluster health status: RED / unassigned shards
- es_rejected_execution_exceptiones_rejected_execution_exception: rejected execution of ... on ... (queue capacity ...) (HTTP 429)
- master_not_discovered_exceptionmaster_not_discovered_exception / MasterNotDiscoveredException
- security_exceptionsecurity_exception: unable to authenticate / action [...] is unauthorized for user [...] (HTTP 401/403)
- validation_exceptionvalidation_exception / illegal_argument_exception: Validation Failed: ...