Skip to content
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

Adding an ILM Action to be able to do snapshot an index during an ILM phase. #51199

Closed
rkalluri-clgx opened this issue Jan 19, 2020 · 8 comments
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management >enhancement Team:Data Management Meta label for data/management team

Comments

@rkalluri-clgx
Copy link

I would like to request an ability to snapshot an index as part of an ILM action (https://www.elastic.co/guide/en/elasticsearch/reference/current/_actions.html)

This would be useful for time based indices especially when using a cloud storage as repository like S3 or GCS to off load the cold data off the elastic cluster

This will provide ways to restore those indices when there is a need to restore specific time based indices.

@rkalluri-clgx
Copy link
Author

I was thinking we can implement this as a generic user provided action / callback that can implement any custom action based on a phase of the lifecycle like providing notifications and such.

@cbuescher cbuescher added :Data Management/ILM+SLM Index and Snapshot lifecycle management >enhancement labels Jan 21, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-features (:Core/Features/ILM+SLM)

@dakrone
Copy link
Member

dakrone commented Jan 21, 2020

@rkalluri-clgx we recently implemented #45067 (#50454) which allows waiting in the delete phase for an SLM policy snapshot to be taken. Does this cover what you're asking for? (the index doesn't have to be deleted)

If not, can you clarify your exact use case?

@rkalluri-clgx
Copy link
Author

I am thinking from the aspect of index archival not backup. This will be like a final read only copy of the index that is closed so that we can replay these back. I treat the SLM to be more for disaster recovery.

@zuketo
Copy link

zuketo commented Feb 14, 2020

Hi @rkalluri-clgx, can you please provide more details on your use case here? I'm trying to understand what "replay these back" means? Would you like to snapshot older indices automatically before deleting them, then have a mechanism for restoring those indices when needed? You may also be interested in freezing indices within ILM, frozen indices will allow you to create very dense nodes for long term data storage.

@cpmoore
Copy link

cpmoore commented Apr 5, 2020

+1 for this feature
For my use case, there are certain indexes where I want to take the number_of_replicas down to 0 after the index is rolled over, however I want to ensure a snapshot exists before I do this (just in the event that the worker node where that index resides is lost beyond recovery)
Therefore i need the snapshot taken as soon as the index is rolled over, but before the index settings change is applied.

@dakrone
Copy link
Member

dakrone commented Apr 13, 2020

Just wanted to point out to folks in this also, that we do have support in ILM for searchable snapshots now: #50806 and in that step, it can be configured to keep the snapshot past the point where the index would be deleted.

@rjernst rjernst added the Team:Data Management Meta label for data/management team label May 4, 2020
@dakrone
Copy link
Member

dakrone commented Dec 9, 2020

For now we are closing this as we don't want to increase the number of single-snapshot indices for backup purposes, as that could cause cluster instability (see #66042)

@dakrone dakrone closed this as completed Dec 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Data Management/ILM+SLM Index and Snapshot lifecycle management >enhancement Team:Data Management Meta label for data/management team
Projects
None yet
Development

No branches or pull requests

7 participants