elasticsearch
Elasticsearch Exceptions
Exception types returned by Elasticsearch. These appear in the type field of an error object in the API response.
12 codes
references elastic.co/guide/en/elasticsearch/reference/current/rest-api-exceptions.htmlelastic.co/guide/en/elasticsearch/reference/current/docs-get.html
· All codes 12 codes
- circuit_breaking_exception Circuit Breaking Exception A circuit breaker was tripped to prevent an operation from causing an OutOfMemoryError. The request used too much memory. Reduce the size of the query, use pagination, or increase the heap size.
- cluster_block_exception Cluster Block Exception The cluster or index has a block that prevents the operation. Common blocks include a read-only block triggered when disk watermarks are breached, or a write block set manually. Check cluster health and disk space.
- document_missing_exception Document Missing Exception The document to be updated or deleted does not exist. This is raised by script-based updates when retry_on_conflict is exhausted. Check that the document ID is correct before updating.
- illegal_argument_exception Illegal Argument Exception An argument passed in the request is invalid. The error message describes which argument is invalid and why. Common causes include unsupported aggregation configurations, invalid field names, and out-of-range parameter values.
- index_not_found_exception Index Not Found Exception The specified index does not exist. Verify the index name, check for typos, and ensure the index has been created before querying it.
- mapper_parsing_exception Mapper Parsing Exception A document field could not be mapped to the type defined in the index mapping. Check that the value type matches the field's mapping type, or update the mapping before indexing.
- no_shard_available_action_exception No Shard Available Action Exception No shard copy is available to serve the request. This usually means the index is red (primary shards are unassigned). Check cluster health, node availability, and disk space.
- query_shard_exception Query Shard Exception A query failed on one or more shards, often due to a field type mismatch (e.g. running a range query on a text field) or an unmapped field. Use ignore_unmapped or ensure the field mapping is correct.
- resource_already_exists_exception Resource Already Exists Exception The index or resource being created already exists. Use the create=false option, or delete the existing resource first.
- search_phase_execution_exception Search Phase Execution Exception One or more shards failed during a search. The root causes are listed in the shard_failures array. Common causes include query syntax errors, field type mismatches, and out-of-memory conditions on shards.
- strict_dynamic_mapping_exception Strict Dynamic Mapping Exception A field was encountered in a document that is not defined in the index mapping, and the index uses strict dynamic mapping. Either add the field to the mapping or change dynamic to true or runtime.
- version_conflict_engine_exception Version Conflict Engine Exception An optimistic concurrency conflict occurred: the document version on the server does not match the expected version in the request. Retry the operation after re-fetching the current document version.