repository_missing_exception: repository_missing_exception
ElasticsearchWhat does it mean?
The snapshot repository referenced in a snapshot/restore operation was not found. No repository is registered under the given name.
Why does it happen?
The repository was never registered, a typo in the name, the repository was deleted, it is defined on a different cluster, or it was not re-registered after the cluster state was reset.
How to fix it
List registered repositories: GET _snapshot/_all. Re-register the repository with the correct name and settings: PUT _snapshot/repo_name (with type and settings). Make sure the repository name is spelled correctly. Verify that access to the shared repository (fs/s3, etc.) works on all nodes.
More from this engine
- script_exceptionscript_exception
- number_format_exceptionnumber_format_exception
- connect_transport_exceptionconnect_transport_exception
- concurrent_snapshot_execution_exceptionconcurrent_snapshot_execution_exception
- invalid_index_name_exceptioninvalid_index_name_exception
- resource_not_found_exceptionresource_not_found_exception
- process_cluster_event_timeout_exceptionprocess_cluster_event_timeout_exception