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

snapshot policy should allow specifying indices #56

Closed
adityaj1107 opened this issue Jun 3, 2021 · 4 comments
Closed

snapshot policy should allow specifying indices #56

adityaj1107 opened this issue Jun 3, 2021 · 4 comments
Labels

Comments

@adityaj1107
Copy link
Contributor

Issue by wyllys66
Monday Jan 11, 2021 at 22:50 GMT
Originally opened as opendistro-for-elasticsearch/index-management#382


Currently, (release 1.12.0), it appears that we cannot specify what indexes to include in a snapshot when the snapshot is triggered by a policy. The policy action for "snapshot" only includes the repository and the name of the snapshot. It should allow for additional parameters related to snapshot operations.

@adityaj1107 adityaj1107 added the enhancement New request label Jun 3, 2021
@adityaj1107
Copy link
Contributor Author

Comment by wyllys66
Wednesday Jan 20, 2021 at 17:22 GMT


While it is possible to create index_templates that assign a snapshot policy to a list of matching indices, the problem with that approach is that it results in a separate snapshot for each index. It would be so much better if there was a single snapshot that included the matching indices. This is pretty significant.

@adityaj1107
Copy link
Contributor Author

Comment by lav-kush
Tuesday May 25, 2021 at 15:18 GMT


Currently, it appears that we cannot specify dynamic snapshot name in ISM policy. The policy action for "snapshot" only includes the repository and the static name of the snapshot, and it creates separate snapshot for each indices with name -. It should allow to pass dynamic snapshot name say for each index something like ctx.index var as used in message template.

thalurur pushed a commit to thalurur/open-index-management that referenced this issue Oct 22, 2021
Signed-off-by: Drew Baugher <46505179+dbbaughe@users.noreply.github.com>
@ynuyasha
Copy link

I agree totally with this. Actually we still using script with curator to aggregate with some logic indexes in one daily snapshot. And we cannot migrate to ISM because a snapshot for every index create a proliferation inside a S3 repository and after that will be difficult to retrieve and manage all snapshots with snapshot api caused by slowness of response do to the high number of snapshots.

@bowenlan-amzn
Copy link
Member

bowenlan-amzn commented Nov 5, 2022

Please check out snapshot management feature https://opensearch.org/docs/latest/opensearch/snapshots/snapshot-management/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants