Details
-
Bug
-
Resolution: Fixed
-
Major
-
7.1.3
-
Untriaged
-
0
-
Unknown
Description
Currently, when we use alter index to update replica count, the new replicas added are not built immediately if the original definition has
{`defer_build`: true}but the existing replicas are built. the new replicas are built as a part of the next iteration of processing create command token. Instead, while creating the index, we should see if the status of the existing instances is ready and trigger build of the new instance if so
Issue | Resolution |
When alter index updated the replica count, new replicas were not built immediately when the original definition was {defer_build: true}. Existing replicas were built and new replicas were built in the next processing iteration. | New replicas are now built when the replica count is updated for deferred indexes. The status of existing index instances is checked, and if ready, a new build of the instance is triggered. |
Attachments
Issue Links
- is a backport of
-
MB-56122 build new replicas when updating replica count for deferred indexes
-
- Resolved
-