Diagnosing invalid repositories
When an Elasticsearch node faces an unexpected exception when trying to instantiate a snapshot repository, it will mark the repository as "invalid" and write a warning to the log file. Use the following steps to diagnose the underlying cause of this issue:
- Retrieve the affected nodes from the affected resources section of the health report.
- Refer to the logs of the affected node(s) and search for the repository name. You should be able to find logs that will contain relevant exception.
- Try to resolve the errors reported.
© 2023-2025 Elasticsearch
As of September 2024, Elasticsearch is available under a choice of three licenses: the Server Side Public License (SSPL), the Elastic License, or the AGPLv3 (OSI approved).
Elasticsearch and the Elasticsearch logo are trademarks of Elasticsearch B.V., registered in the U.S. and in other countries.
https://www.elastic.co/guide/en/elasticsearch/reference/8.17/diagnosing-invalid-repositories.html
