-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Labels:None
Fail reconfig for shard server if it would change DWCF and CWWC is not set
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. We should only do that if the DWCF changes to w:1. We should not be holding any locks when we poll the config server and likely should do this at the beginning of the reconfig command, before we acquire the replication coordinator mutex.
- documents
-
SERVER-56846 Fail reconfig for shard server if it would change DWCF and CWWC is not set
- Closed
- duplicates
-
DOCS-14677 Investigate changes in SERVER-56800: Fail addShard if CWWC disagrees with existing CWWC on cluster
- Closed
- is related to
-
DOCS-14643 Investigate changes in SERVER-56845: Fail addShard if DWCF=w:1 and no CWWC is set
- Closed