bowenlan-amzn

In error prevention, we should be able to identify the current stage of the index (hot, warm, cold), some actions are not runnable for warm/cold stage. Considering enforce adopting the...

Do you want to try continuous mode rollup, and set the running schedule to be 30m

Remember there's an example from the [documentation](https://opensearch.org/docs/latest/im-plugin/index-rollups/index/#example) that seems to help here. Pls let us know if whether it's working.

Got it, the rollup created by ISM action is fixed to be non-continuous https://github.com/opensearch-project/index-management/blob/a2dd769f8ca62b45d89b8ba6e0d32770eeebf1ae/src/main/kotlin/org/opensearch/indexmanagement/rollup/model/ISMRollup.kt#L80 If this data class ISMRollup supports user to provide continuous parameter, then I think using ISM...

We will plan this, thanks!

@DucQuach I checked the 2 error messages you mentioned `"heap usage exceeded", "elapsed time exceeded"`, seems these are from search backpressure feature, would you want to try tune the settings...

I see, would you reach out to AWS support and ask them to cut a ticket to the service team regarding this issue.

@soosinha please go ahead. We have [a request](https://github.com/opensearch-project/index-management/issues/734) to copy over all aliases from previous index to newly created index during rollover, will your enhancement also cover aliases or it...

Thanks a lot! I would suggest using separate parameters for aliases, settings and mappings.

@aggarwalShivani Thanks for spending time on this! 1,2 I think we can introduce new field under `deletion` in [create policy API](https://opensearch.org/docs/latest/tuning-your-cluster/availability-and-recovery/snapshots/sm-api/#create-or-update-a-policy) This new field contains the delete snapshot name pattern...