IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Diagnosing unknown repositories Addressing repeated snapshot policy failures »
Elastic Docs ›Elasticsearch Guide [8.15] ›Troubleshooting ›Troubleshooting broken repositories

Diagnosing invalid repositories

edit

Diagnosing invalid repositories

edit

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:

  1. Retrieve the affected nodes from the affected resources section of the health report.
  2. 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.
  3. Try to resolve the errors reported.
« Diagnosing unknown repositories Addressing repeated snapshot policy failures »