[DOCS-14643] Investigate changes in SERVER-56845: Fail addShard if DWCF=w:1 and no CWWC is set Created: 13/Jul/21  Updated: 13/Nov/23  Resolved: 16/Nov/21

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.1.0-rc0, 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: Ian Fogelman
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backports DOCS-14722 [BACKPORT] [v5.0] Fail addShard if DW... Closed
Documented
documents SERVER-56845 Fail addShard if DWCF=w:1 and no CWWC... Closed
Related
related to DOCS-14644 Investigate changes in SERVER-56844: ... Closed
related to DOCS-14701 [SERVER] Investigate changes in SERVE... Closed
Participants:
Days since reply: 2 years, 19 weeks, 5 days ago
Epic Link: DOCSP-14300

 Description   
Downstream Change Summary

We need to document the new error will be raised during running "addShard" command if DWCF (default write concern formula) =w:1 and no CWWC (Clsuter wide write concern) is set

Description of Linked Ticket

The config server could request the replica set's config as part of the validation in _validateHostAsShard to be able to see what the result of the DWCF would be.

This might be unnecessary depending on the implementation for SERVER-56844.



 Comments   
Comment by PM Bot [ 24/Sep/21 ]

Downstream changes updated for upstream SERVER-56845:
We need to document the new error will be raised during running "addShard" command if DWCF (default write concern formula) =w:1 and no CWWC (Clsuter wide write concern) is set

This ticket was reverted in 5.0 because it is incompatible with Ops Mgr. However it will be in 5.1.

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