Hi,
I have a follow up question in the process described in “How to migrate Visibility database”. Assuming I want to migrate from one ElasticSearch index to another (eg to rectify a too low primary shard count), can I create the new index with the correct settings, enable dual write and then start a ElasticSearch _reindex operation to index existing data from the old into the new index?
We have long/indefinitely running workflows, so the advice from the docs to wait for the retention period to be reached does not quite work for us.
- To manage closed Workflow Executions data, run in dual mode until the Namespace Retention Period is reached. After the Retention Period, Workflow Execution data is removed from the Persistence and Visibility stores. If you want to keep the closed Workflow Executions data after the set Retention Period, you must set up Archival.
In this scenario we would be setting the setting the conflicts:proceed setting of the _reindex API call.
Does this sounds reasonable? Has anyone tried this approach?
Thanks,
Hardy