-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
Searchable snapshot should not be able to be deleted if it's in use by a frozen index #108450
Labels
>bug
:Distributed/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>docs
General docs changes
Team:Distributed
Meta label for distributed team
Team:Docs
Meta label for docs team
Comments
kunisen
added
>bug
needs:triage
Requires assignment of a team area label
:Distributed/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
labels
May 9, 2024
elasticsearchmachine
added
Team:Data Management
Meta label for data/management team
Team:Distributed
Meta label for distributed team
labels
May 9, 2024
Pinging @elastic/es-distributed (Team:Distributed) |
Pinging @elastic/es-data-management (Team:Data Management) |
elasticsearchmachine
removed
the
needs:triage
Requires assignment of a team area label
label
May 9, 2024
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
May 9, 2024
The word `cannot` implies Elasticsearch prevents you from doing these things, but it doesn't have this protection today (see elastic#73947). This commit clarifies this by saying `must not` instead. Closes elastic#108450
DaveCTurner
added
>docs
General docs changes
and removed
:Data Management/ILM+SLM
Index and Snapshot lifecycle management
Team:Data Management
Meta label for data/management team
labels
May 9, 2024
Pinging @elastic/es-docs (Team:Docs) |
DaveCTurner
added a commit
that referenced
this issue
May 9, 2024
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
May 9, 2024
The word `cannot` implies Elasticsearch prevents you from doing these things, but it doesn't have this protection today (see elastic#73947). This commit clarifies this by saying `must not` instead. Closes elastic#108450
DaveCTurner
added a commit
to DaveCTurner/elasticsearch
that referenced
this issue
May 9, 2024
The word `cannot` implies Elasticsearch prevents you from doing these things, but it doesn't have this protection today (see elastic#73947). This commit clarifies this by saying `must not` instead. Closes elastic#108450
elasticsearchmachine
pushed a commit
that referenced
this issue
May 9, 2024
elasticsearchmachine
pushed a commit
that referenced
this issue
May 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Distributed/Snapshot/Restore
Anything directly related to the `_snapshot/*` APIs
>docs
General docs changes
Team:Distributed
Meta label for distributed team
Team:Docs
Meta label for docs team
Elasticsearch Version
8.13.3
Installed Plugins
No response
Java Version
bundled
OS Version
major
Problem Description
We found a doc bug for searchable snapshot. (cc @geekpete)
Description
The searchable snapshot doc says this:
But we found actually we can delete even it’s mounted. Please see the screenshot.
Our concern
:: [1]
It literally means we have no protection to searchable snapshot, even it’s being mounted to frozen indices. People have deletion permission can delete it.
(We are not talking about deleting the frozen index, but only talking about deleting searchable snapshot directly)
Can we add this guardrail logic to make this statement become really true, or at least remove this part?
:: [2]
Also, if a customized SLM wants to delete searchable snapshot, it should error out too, based on the same context.
Our testing result:
Reference
Steps to Reproduce
Prepare frozen index and searchable snapshot
Check searchable snapshot is created and try delete it
Logs (if relevant)
No response
The text was updated successfully, but these errors were encountered: