Details
Description
Currently, we persist the 'commitQuorum' value that user provided for createIndexes cmd, into "config.system.IndexBuilds collection, only on receiving first ready to commit vote by primary. If current primary gets restarted/rolled back before receiving any votes, and gets re-elected, then new primary would not know about the commit quorum value. Currently, we crash our system. As, our current contract is, two phase index build should have a commit quorum value set.
To be noted, all the nodes who are eligible to become primary should have the commit quorum value, as the 2 phase index build can survive state transition and any node can act as coordinator for the 2 phase index build.
Attachments
Issue Links
- is depended on by
-
SERVER-46659 Make initial sync work with two phase index builds + commit quorum on
-
- Closed
-
-
SERVER-47461 Remove commit quorum value from StartIndexBuild oplog entry
-
- Closed
-
- is duplicated by
-
SERVER-46814 Invariant on "Commit quorum is missing for index build"
-
- Closed
-
-
SERVER-46829 Make setIndexCommitQuorum cmd to behave correctly with 2 phase index builds.
-
- Closed
-
- is related to
-
SERVER-46814 Invariant on "Commit quorum is missing for index build"
-
- Closed
-
- related to
-
SERVER-47463 SetIndexCommitQuorum cmd should be supported only for FCV 4.4+ and if 'enableCommitQuorum' = true.
-
- Closed
-