shard_not_found_exception: Shard not found
ElasticsearchWhat does it mean?
The target shard was not found. Elasticsearch could not complete the request because it could not reach the relevant shard of the specified index.
Why does it happen?
The shard is not yet assigned (unassigned) or is in recovery; the shard is temporarily missing because a node left the cluster; or a low-level request routed directly to a shard carries routing information that is no longer valid. It appears when cluster health is degraded.
How to fix it
Check cluster and shard health: GET _cluster/health and GET _cat/shards?v. See why shards are unassigned: GET _cluster/allocation/explain. If a node was lost, bring it back; review disk/allocation settings (watermark). If recovery is in progress, wait for it to finish. Keep an adequate replica count so data stays available when a single node is lost.
More from this engine
- snapshot_missing_exceptionSnapshot is missing
- index_template_missing_exceptionIndex template is missing
- settings_exceptionInvalid settings
- not_x_content_exceptionCompressor detection error / body is not valid content
- document_source_missing_exceptionDocument source is missing
- node_not_connected_exceptionNode is not connected
- receive_timeout_transport_exceptionRequest timed out waiting for a response from another node