[SERVER-72696] Handle cluster wide default read write concern with catalog shard Created: 10/Jan/23  Updated: 29/Oct/23  Resolved: 17/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Jack Mulrow Assignee: Kshitij Gupta
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-74975 Complete TODO listed in SERVER-72696 Closed
Assigned Teams:
Sharding NYC
Backwards Compatibility: Fully Compatible
Sprint: Sharding NYC 2023-02-06, Sharding NYC 2023-02-20, Sharding NYC 2023-03-06, Sharding NYC 2023-03-20
Participants:

 Description   

The cluster wide read and write concern code has logic in a sharded cluster to run commands on the config server at startup and replica set reconfig and SERVER-72454 disabled the startup command when running on a catalog shard (ie user data bearing config server). The startup logic seems unnecessary because on a catalog shard the default RWC should exist locally and the local defaults cache should be enough, but the purpose of this ticket is to verify that and any other behaviors related to default RWC on a catalog shard.



 Comments   
Comment by Githook User [ 16/Mar/23 ]

Author:

{'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}

Message: SERVER-72696: Clarify CWWC field comment.
Branch: master
https://github.com/mongodb/mongo/commit/9bfe18480edaa6761f283a6981f9231434bdb152

Generated at Thu Feb 08 06:22:33 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.