Description
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.
Attachments
Attachments
Issue Links
- is a clone of
-
OAK-9004 Multitenant index name strategy with reindex support
-
- Closed
-