resource_not_found_exception: resource_not_found_exception
ElasticsearchWhat does it mean?
The requested resource (document, index, task, pipeline, model, etc.) was not found. No resource exists for the given ID/name.
Why does it happen?
A nonexistent document ID, an index/pipeline that was deleted or never created, a misspelled name, a task not yet completed or already cleaned up, or a request sent to the wrong cluster.
How to fix it
Verify the resource name/ID and that it exists (e.g. GET /index/_doc/id, GET _ingest/pipeline/name). Make sure you are sending the request to the correct index and cluster. Review the order of delete/create operations. For tasks, check the status with the _tasks API.
More from this engine
- repository_missing_exceptionrepository_missing_exception
- concurrent_snapshot_execution_exceptionconcurrent_snapshot_execution_exception
- invalid_index_name_exceptioninvalid_index_name_exception
- process_cluster_event_timeout_exceptionprocess_cluster_event_timeout_exception
- search_context_missing_exceptionNo search context found for id (scroll expired)
- aliases_not_found_exceptionAliases missing
- snapshot_missing_exceptionSnapshot is missing