[
https://issues.apache.org/jira/browse/OAK-9053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amrit Verma resolved OAK-9053.
------------------------------
Resolution: Fixed
We decided to implement the simple (first) approach now.
> Reindexing Strategy for ES indexes
> ----------------------------------
>
> Key: OAK-9053
> URL: https://issues.apache.org/jira/browse/OAK-9053
> Project: Jackrabbit Oak
> Issue Type: Task
> Components: indexing
> Reporter: Amrit Verma
> Priority: Major
> Fix For: 1.28.0
>
> Attachments: OAK-9053-new.patch
>
>
> There are two approaches for handling re-indexing of ES indexes.
> The simpler strategy would be to:
> * create the new index
> * move writes and reads to the new index
> * delete old index
> A more sophisticated strategy could:
> * create the new index
> * move writes to the new index
> * reads will continue to use the old index until the new one catches up
> * when the new one is in sync, move reads to the new index & delete the old
> one
> Both strategies can be implemented using Aliases in Elasticsearch to avoid
> race conditions. To implement the second solution we need something that
> tells us when the new index has caught up with the initial load.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
