opensearch-project / index-management

🗃 Automate periodic data operations, such as deleting indices at a certain age or performing a rollover at a certain size
https://opensearch.org/docs/latest/im-plugin/index/
Apache License 2.0
53 stars 108 forks source link

[FEATURE] Support management of replicated indices #1061

Open mmehrten opened 7 months ago

mmehrten commented 7 months ago

Is your feature request related to a problem? When a cluster uses Cross-Cluster Replication, the follower index gets marked as read only. This means ISM actions can't be used with a follower index unless the index explicitly stops replication. ISM should allow a follower index to have transition actions performed like migrating to warm/cold (e.g. the follower cluster should be able to mirror the leader cluster's ISM actions).

What solution would you like? Follower clusters are able to use ISM actions to roll over and index to warm/cold tiers after the follower is caught up to the leader.

What alternatives have you considered? Manually implementing this with an external automation (e.g. cron jobs, lambdas, etc.)

dblock commented 4 weeks ago

Catch All Triage - 1 2 3 4 5