[SERVER-43769] Only get the default write concern from ReplSetConfig if no write concern is specified Created: 02/Oct/19  Updated: 29/Oct/23  Resolved: 05/Oct/19

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

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

Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-10-07
Participants:

 Description   

Currently, we call getGetLastErrorDefault every time extractWriteConcern is called even though a write concern is already specified. For {w: majority}, this means that we have an unnecessary serialization point in extractWriteConcern. We can change this to be on-demand to avoid locking the ReplicationCoordinator mutex.



 Comments   
Comment by Githook User [ 05/Oct/19 ]

Author:

{'username': 'ldennis', 'email': 'lingzhi.deng@mongodb.com', 'name': 'Lingzhi Deng'}

Message: SERVER-43769: Only get the default write concern from ReplSetConfig if no write concern is specified
Branch: master
https://github.com/mongodb/mongo/commit/150dfeceb607bb40bbae2e5a49ad9bca08f13e25

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