[SERVER-73474] Fix ReplicationCoordinator::runCmdOnPrimaryAndAwaitResponse header comment Created: 31/Jan/23  Updated: 17/Feb/23  Resolved: 17/Feb/23

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

Type: Improvement Priority: Major - P3
Reporter: Yujin Kang Park Assignee: Backlog - Storage Execution Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-73294 Signal primary node for aborting inde... Closed
Assigned Teams:
Storage Execution
Participants:

 Description   

Comment states cmd will run on a DBDirectClient if the node is primary, or AsyncDBClient otherwise. After SERVER-48235 this is no longer true, and the command always runs with AsyncDBClient.

https://github.com/10gen/mongo/blob/b62723290a994c445b9f1740c642fce79ffe07bd/src/mongo/db/repl/replication_coordinator.h#L1141


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