Rollover on min_index_age clashes with Reindexing?

[activeperception]

Hi,

We've setup ISM to rollover/transition based on min_index_age but we realized that reindexing clashes with it. After reindexing the new index gets a new creation date and the policy running on min_index_age gets obviously delayed.

Is there a workaround anyone can think of? AFAIK it's possible to override the creation date for an index in Elastic but not with Opendistro, maybe that would be enough to fix the issue.

Alternatively reindex could be changed to copy over, optionally, the original index metadata (creation time in this case).

Thanks for your help, Raffaele

[IzekChen]

Hi @activeperception,

I am also experiencing the same issue, but I dont know what timestamp filed casue the problem. Can you explain a bit more, please?

[activeperception]

@IzekChen

It's not a timestamp you can control, it's the index creation date that gets reset when reindexing.

I couldn't find a workaround and, at the time, opted for not using the reindex api and, instead, wrote a script that scans through all documents and saves them again in place.