[SERVER-64309]  Modify the server to support the setRWConcernDefault command directly against shardsvrs Created: 07/Mar/22  Updated: 06/Dec/22  Resolved: 08/Mar/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: 6.0 Desired
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Sophia Tan Assignee: [DO NOT USE] Backlog - Server Serverless (Inactive)
Resolution: Won't Do Votes: 0
Labels: ordered
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-60817 setDefaultRWConcern accepts invalid w... Closed
is related to SERVER-61864 Replica set reconfiguration should ch... Closed
Assigned Teams:
Serverless
Participants:

 Description   

Modify the server to support the setRWConcernDefault command directly against shardsvrs. 

Do similar to getRWConcernDefault command.



 Comments   
Comment by Esha Maharishi (Inactive) [ 08/Mar/22 ]

max.hirschhorn, hmm, thanks for pointing out SERVER-60817. The motivation was to support upgrading the mongod layer of Serverless to shardsvrs before introducing mongoq. However, I just confirmed with Louisa that setRWConcernDefault isn't supported in Serverless, so we don't need to make this change.

Closing as Won't Do.

 

Comment by Max Hirschhorn [ 07/Mar/22 ]

Could the motivation for this change be expanded upon? In particular, the changes from SERVER-60817 opted to not attempt to validate the replica set tags in a sharded cluster because the setRWConcernDefault isn't ever run against a --shardsvr.

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