-
Notifications
You must be signed in to change notification settings - Fork 24.6k
-
Notifications
You must be signed in to change notification settings - Fork 24.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide API to identify dangling searchable snapshots #113168
Comments
Pinging @elastic/es-distributed (Team:Distributed) |
I'm not really sure that we can reliably identify such snapshots, there's nothing particularly special about these snapshots vs any other snapshots the user might have taken. If the user is only using SLM and ILM to take snapshots then you can identify all non-SLM snapshots with |
Description
What is a dangling searchable snapshot?
It is a searchable snapshot stored in a snapshot repository and no longer referenced/used by an Elasticsearch cluster. This can happen in the following situations:
If users manually delete an index or data stream before ILM
delete
phase runs, then ILM will not delete the underlying searchable snapshot. Users would need to use the Delete snapshots API to remove the searchable snapshot from the snapshot repository when it is no longer needed.delete
phase but thedelete_searchable_snapshot
is set tofalse
(c.f Delete). Users would need to use the Delete snapshots API to remove the searchable snapshot from the snapshot repository when it is no longer needed.How to determine if a searchable snapshot is dangling?
As of the time of writing, Elasticsearch does not provide an API to retrieve such information. Manual checks need to be done which could very tedious and error-prone.
Motivation
The text was updated successfully, but these errors were encountered: