[DOCS-13518] Investigate changes in SERVER-46658: Implement commit quorum option "all" Created: 16/Mar/20 Updated: 13/Nov/23 Resolved: 25/Mar/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | docs-query | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Participants: | |||||||||||||
| Days since reply: | 3 years, 47 weeks, 2 days ago | ||||||||||||
| Epic Link: | DOCS: 4.4 Server Release Work | ||||||||||||
| Description |
DescriptionDownstream Change Summary Execution team has introduced a new option named ‘commitQuorum’ to ‘createIndexes’ command as part of PM-253 (Two phase commit for index build). ‘commitQuorum’ is very similar to writeConcern options which can accept an integer or a string - “majority”and custom write concern option. In addition to those values, the new ‘commitQuorum’ option will also accept “all” string value. A primary node that coordinates an index build can’t complete an index build until it has received votes from secondaries stating that they have each finished collection scanning and draining phase for that index build. The number of votes the primary has to wait before committing an index depends on the commitQuorum option’s value. The primary is also eligible to vote and it will vote for itself. The main purpose of this new ‘commitQuorum’ option is to prevent slow secondaries replication from getting blocked on applying ‘commitIndexBuild’ oplog entry waiting for the index build completion on that secondary. The current default value for the ‘commitQuorum’ option in 4.4 RC0 is “majority”, i.e., majority of voting data bearing nodes. Currently, some implementation issues with initial sync and abort index build logic have prevented us from making the default value for ‘commitQuorum’ as ‘all’, i.e., all voting data bearing nodes. For MongoDB 4.4 GA, the default value for ‘commitQuorum’ will be ‘all’ and we are working towards making the default value change ( For a quick reference, if a user wants to create an index ‘x_1’ on foo.bar collection with a commit quorum value as “all”, then the shell syntax will be: Description of Linked TicketLike we have "majority" for commit quorum value, we should support commit quorum option "all" which means all data bearing voting members in a replica set. Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |