repository_verification_exception: repository_verification_exception

What does it mean?

While a snapshot repository was being registered or verified, the check that all nodes can access the repository failed. Because repository verification did not pass, snapshot/restore operations cannot be performed reliably.

Why does it happen?

A shared file system (fs) repository is not mounted/accessible at the same path on all nodes, path.repo is missing from the configuration, file permissions are insufficient, or cloud/object stores (S3, GCS, Azure) have incorrect credentials/network access. Some nodes being unable to write to the repository is the typical cause.

How to fix it

For a shared fs repository, make sure path.repo is defined in elasticsearch.yml on all nodes and that the same path is mounted readable/writable on every node. Fix file permissions (elasticsearch user). For cloud repositories, verify credentials (keystore), the bucket name and network/access permissions. Re-verify the repository with POST _snapshot/repo/_verify.