Each week, our automated system is scheduled to remove existing snapshots and upload new ones to the Azure blob storage containers. However, once the fresh snapshots are uploaded, the Kibana dashboard displays 'No snapshot information' for the 'default' client's Azure repository.
Additionally, when utilizing the API, I encounter a 'Snapshot missing exception.' This exception refers to snapshots that have already been erased. It's unclear why Elasticsearch attempts to access snapshots that no longer exist. As a temporary workaround, manually deleting and recreating the repository on the dashboard resolves the problem.
[root@VM0D tech]# curl -XGET -u elastic:*** --insecure https://localhost:9200/_snapshot/distribution/_all?pretty
{
"error" : {
"root_cause" : [
{
"type" : "snapshot_missing_exception",
"reason" : "[distribution:company-subsidiary-2023.11.28-06.45.43/sKwDYOMQTs-1cF0k&6TgHw] is missing"
}
],
"type" : "snapshot_missing_exception",
"reason" : "[distribution:company-subsidiary-2023.11.28-06.45.43/sKwDYOMQTs-1cF0k&6TgHw] is missing",
"caused_by" : {
"type" : "no_such_file_exception",
"reason" : "Blob [snap-sKwDYOMQTs-1cF0k&6TgHw.dat] not found"
}
},
"status" : 404
}
Similar workaround suggested by Elastic forum Missing Snapshot Error
Is there a more permanent solution available? We began experiencing this issue following an upgrade from version 7.17 to 8.10 across all our environments, both lower and higher.