[DOCS-14644] Investigate changes in SERVER-56844: Fassert shard server on startup if DWCF=w:1 and no CWWC 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:
Documented
documents SERVER-56844 Fassert shard server on startup if DW... Closed
Related
is related to DOCS-14643 Investigate changes in SERVER-56845: ... Closed
Participants:
Days since reply: 2 years, 19 weeks, 5 days ago
Epic Link: DOCSP-14300
Story Points: 2

 Description   
Downstream Change Summary

We need to add this assertion to our docs.

Description of Linked Ticket

Since the shard server doesn't have the CWWC in memory, it will need to poll the config server for that information. This should be safe to do before we set the shard as initialized, since we will block commands from mongos until the shard is initialized.



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

Downstream changes updated for upstream SERVER-56844:
We need to add this assertion to our docs.

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:52 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.