GET _snapshot/_status returns 404 "repository_missing_exception" even though the repository exists and works

Elastic Stack Elasticsearch
1

I'm using Elasticsearch 6.8.3

The reason I discovered this is because curator calls GET _snapshot/_status before it starts doing snapshots, and it is failing with a 404 response.

I've confirmed that the response to that call is indeed:

{
  "error": {
    "root_cause": [
      {
        "type": "repository_missing_exception",
        "reason": "[_all] missing"
      }
    ],
    "type": "repository_missing_exception",
    "reason": "[_all] missing"
  },
  "status": 404
}

But.... this is really strange because I can successfully backup and restore snapshots in my repository. I've tried re-creating it with no help.

The repository settings are:

    {
      "dev-es6-backup-repository": {
        "type": "fs",
        "settings": {
          "location": "\\\\sanitizedserver\\elasticsearch_backup_repos\\dev-es6-backup-repository"
        }
      }
    }
2

Which version of Curator are you using?

$ curator --version
curator, version 5.8.4
3

Thanks,
I forgot to mention I also updated curator to the latest version to see if it would help. No luck.

curator.exe, version 5.8.4

It seems more like an ES problem since it is returning the 404 error.

4

I would have to deploy Elasticsearch 6.8.3 to see, but I'm kind of leaning towards a change in how Elasticsearch worked with _all that came after . Curator has been integration tested against 6.8.15 and does not have this problem.

5

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.