[SERVER-62016] Write concern accepts embedded replica set tagset Created: 13/Dec/21  Updated: 29/Oct/23  Resolved: 13/Jan/22

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

Type: Task Priority: Major - P3
Reporter: Matt Broadstone Assignee: Matt Broadstone
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Server Serverless 2021-12-27, Server Serverless 2022-01-10, Server Serverless 2022-01-24
Participants:
Linked BF Score: 150

 Description   

Support requesting acknowledgement that a write operation has propagated to a specified number of tagged nodes, without requiring users to define a custom write concern in the replica set config. Accept a write concern with the custom write concern specification embedded in the w option:

db.collection.insertOne(
   { id: "xyz", status: "A" },
   { writeConcern: { w: { "dc_va": 2, "dc_ca": 1 } } }
)



 Comments   
Comment by Githook User [ 13/Jan/22 ]

Author:

{'name': 'Matt Broadstone', 'email': 'mbroadst@mongodb.com', 'username': 'mbroadst'}

Message: SERVER-62016 support tagged write concerns
Branch: master
https://github.com/mongodb/mongo/commit/364268284a6131c04e7abed051e5851479dceb6d

Generated at Thu Feb 08 05:53:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.