[DOCS-15166] Investigate changes in SERVER-63531: commitQuorum error message incorrectly says that only voting nodes are eligible Created: 10/Mar/22  Updated: 29/Oct/23  Resolved: 18/Apr/22

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: 5.0.0, 5.3.0, 6.0.0
Fix Version/s: 6.0.0-rc0, 5.0.8, 5.3.2

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Ashley Brown
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-15233 [BACKPORT] [v5.0] commitQuorum incorr... Closed
backported by DOCS-15238 [Server: BACKPORT] [v5.3] commitQuoru... Closed
Documented
documents SERVER-63531 commitQuorum incorrectly includes bui... Closed
Participants:
Days since reply: 1 year, 43 weeks ago
Epic Link: DOCSP-19446
Story Points: 2

 Description   
Original Downstream Change Summary

The following changes have been made:

  • Error messages have been updated to indicate that non-voting nodes may be included in an index build commitQuourm. Our documentation incorrectly states that commitQuorum only includes "data-bearing voting replica set members". This should be updated to say "data-bearing replica set members"
  • Nodes with buildIndexes:false can never be included in a commitQuorum. Previously, we incorrectly allowed non-voting buildIndexes:false nodes to be part of a commitQuorum, but these nodes should never be included, regardless of voting status.

    Description of Linked Ticket

    The commitQuorum option for index builds does not allow non-voting nodes to participate. With the default commitQuorum of "votingMembers", a lagged non-voting secondary, like an analytics node, can fall behind. Other voting nodes will commit, but when this secondary receives a commitIndexBuild oplog entry, it stalls until the index build completes.

There is currently no way to use commitQuorum to include the non-voting node to prevent this from happening.

commitQuorum does allow you to include non-voting nodes, however the error message we report "Not enough data-bearing voting nodes to satisfy commit quorum" is incorrect. We should also update the documentation to reflect this.



 Comments   
Comment by Jess Mokrzecki [ 13/Apr/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0-rc0, 5.3.2, 5.0.8

Comment by Ashley Brown [ 12/Apr/22 ]

Hi louis.williams@mongodb.com, I've made changes to the docs based on the work you did in SERVER-63531. Could you give the PR a technical review? Thank you!

Comment by Jess Mokrzecki [ 12/Apr/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0-rc0, 5.0.8

Comment by Jess Mokrzecki [ 28/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0-rc0

Comment by Jess Mokrzecki [ 28/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0, 6.0.0-rc0

Comment by Jess Mokrzecki [ 22/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0

Comment by Jess Mokrzecki [ 22/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0, 5.0.7

Comment by Jess Mokrzecki [ 22/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0

Comment by Jess Mokrzecki [ 22/Mar/22 ]

Fix Version updated for upstream SERVER-63531:

Comment by Jess Mokrzecki [ 16/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0, 5.0.7

Comment by Jess Mokrzecki [ 10/Mar/22 ]

Fix Version updated for upstream SERVER-63531:
6.0.0

Generated at Thu Feb 08 08:12:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.