-
Type: Improvement
-
Resolution: Won't Fix
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Storage Execution
-
Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03, Execution Team 2023-04-17, Execution Team 2023-05-29
There have been several occurrences in Atlas where one or more secondary nodes already have an index built that the primary does not have. We think this is due to interrupted rolling index builds. Creating the same index on the primary may result in the index build stalling indefinitely as the secondary nodes with the index will return early and skip voting for the index's commit quorum.
The workaround is to adjust the commit quorum using the setIndexCommitQuorum command.
It would be ideal if secondary nodes with the index already existing could participate in voting for the commit quorum to avoid this.
- is related to
-
SERVER-71769 Add a new log message when a secondary node is skipping a two-phase index build
- Closed
-
SERVER-77311 Add a new log message when a secondary node is skipping a two-phase index build with a subset of indexes built
- Closed
- related to
-
SERVER-77451 Complete TODO listed in SERVER-71768
- Closed