index_not_found_exception: index_not_found_exception: no such index [index_name] (HTTP 404)
ElasticsearchWhat does it mean?
The requested index (or alias) does not exist. The operation was rejected with HTTP 404 because no index with the given name was found.
Why does it happen?
The index was never created, was deleted, the index/alias name has a typo, the client is connected to the wrong environment (cluster), or a write to a nonexistent index was attempted while action.auto_create_index is disabled.
How to fix it
List existing indices: GET _cat/indices?v. Verify the name and alias: GET _alias. Create the index: PUT /index-name (with the required mappings/settings), or configure automatic creation with an index template. If automatic creation is desired, check the action.auto_create_index setting. Verify that you are not connected to the wrong cluster.
More from this engine
- too_many_clausestoo_many_clauses: maxClauseCount is set to 1024 (query contains too many clauses)
- version_conflict_engine_exceptionversion_conflict_engine_exception: [_doc][id]: version conflict, current version [x] is different than the one provided [y] (HTTP 409)
- document_missing_exceptiondocument_missing_exception: [_doc][id]: document missing
- resource_already_exists_exceptionresource_already_exists_exception: index [index_name/uuid] already exists (HTTP 400)
- cluster_health_redcluster health status: RED / unassigned shards
- no_shard_available_action_exceptionno_shard_available_action_exception: No shard available for [...]
- es_rejected_execution_exceptiones_rejected_execution_exception: rejected execution of ... on ... (queue capacity ...) (HTTP 429)