[DOCS-16245] [SERVER] 4.4 and 5.0 doc incorrectly states that if _secondaryThrottle write concern is empty, it is automatically set to majority Created: 06/Jul/23  Updated: 13/Nov/23  Resolved: 06/Sep/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 4.4.0-rc11, 5.0.0-rc7
Fix Version/s: 4.4.0, 5.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Critical - P2
Reporter: Enrico Golfieri Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: bugfix, quick-win
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 24 weeks, 1 day ago

 Description   

After the investigation of HELP-47174 we realised the documentation for 4.4 and 5.0 mentioned that _secondaryThrottle=true will set automatically wc to majority in case is left empty for moveChunk.

However, this is actually true only starting from 6.0 and for previous versions wc is mandatory. 

This is important because in case of balancing, the moveChunk will inherit directly the configuration of the balancer, which might have an empty wc causing the entire balancing to block.

 

Correct the 4.4 and 5.0 doc to note that this setting is required and does not have a default value.

Current published docs:

v4.4
v5.0



 Comments   
Comment by Sarah Olson [ 22/Aug/23 ]

Increasing priority due to associated HELP ticket. 

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