mirror of
https://github.com/honeymoose/OpenSearch.git
synced 2025-02-09 14:35:04 +00:00
100d2bd063
* [DOCS] Editorial cleanup * Moved example of applying a template to multiple indices. * Combine existing indices topics * Fixed test * Add skip rollover file. * Revert rename. * Update include. * Revert rename * Apply suggestions from code review Co-authored-by: Adam Locke <adam.locke@elastic.co> Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com> * Apply suggestions from code review * Fixed callout * Update docs/reference/ilm/ilm-with-existing-indices.asciidoc Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com> * Update docs/reference/ilm/ilm-with-existing-indices.asciidoc Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com> * Apply suggestions from code review * Restored policy to template example. * Fixed JSON parse error Co-authored-by: Adam Locke <adam.locke@elastic.co> Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com> Co-authored-by: Adam Locke <adam.locke@elastic.co> Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com>
29 lines
1.4 KiB
Plaintext
29 lines
1.4 KiB
Plaintext
[role="xpack"]
|
|
[testenv="basic"]
|
|
[[index-lifecycle-and-snapshots]]
|
|
== Restore a managed index
|
|
|
|
When you restore a snapshot that contains managed indices,
|
|
{ilm-init} automatically resumes executing the restored indices' policies.
|
|
A restored index's `min_age` is relative to when it was originally created or rolled over,
|
|
not its restoration time.
|
|
Policy actions are performed on the same schedule whether or not
|
|
an index has been restored from a snapshot.
|
|
If you restore an index that was accidentally deleted half way through its month long lifecycle,
|
|
it proceeds normally through the last two weeks of its lifecycle.
|
|
|
|
In some cases, you might want to restore a managed index and
|
|
prevent {ilm-init} from immediately executing its policy.
|
|
For example, if you are restoring an older snapshot you might want to
|
|
prevent it from rapidly progressing through all of its lifecycle phases.
|
|
You might want to add or update documents before it's marked read-only or shrunk,
|
|
or prevent the index from being immediately deleted.
|
|
|
|
To prevent {ilm-init} from executing a restored index's policy:
|
|
|
|
1. Temporarily <<ilm-stop,stop {ilm-init}>>. This pauses execution of _all_ {ilm-init} policies.
|
|
2. Restore the snapshot.
|
|
3. <<ilm-remove-policy,Remove the policy>> from the index or perform whatever actions you need to
|
|
before {ilm-init} resumes policy execution.
|
|
4. <<ilm-start,Restart {ilm-init}>> to resume policy execution.
|