-
Type: Improvement
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 10.10-HF55, 2021.12
-
Component/s: Elasticsearch
-
Release Notes Summary:It is now possible to perform a full reindexing of the repository without any interruption of service.
-
Tags:
-
Upgrade notes:
-
Team:PLATFORM
-
Sprint:nxplatform #43, nxplatform #44, nxplatform #45, nxplatform #46, nxplatform #47, nxplatform #48, nxplatform #49
-
Story Points:2
There is currently several methods to perform re-indexing, with more or less service interruption and resilience, but none of them allow to fully rebuild an index without any service interruption. By no service interruption I mean:
1/ I start a full re-indexing (that may last several hours if I am on a huge repository)
2/ during that time I create or update content
3/ while re-indexing is happening, my Elasticsearch queries are redirected to the old index and take into account the new repository updates
4/ as soon as my index is rebuilt, Elasticsearch queries use the new index that contains all the latest updates.
The period during which index is not up to date should be minimaliazed at most, if not inexistant.
- causes
-
NXP-30755 Fix ES manage alias feature in HF55 with MongoDB
- Resolved
- is related to
-
NXP-30416 Starting a node while reindexing should not update the write alias index
- Resolved
-
NXDOC-2399 Document the new reindexing without service interruption
- Resolved
- Is referenced in