[SERVER-23344] Resolve dependency of parallel.cpp on ReplicaSetMonitor Created: 25/Mar/16  Updated: 06/Dec/22  Resolved: 05/Dec/16

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

Type: Task Priority: Major - P3
Reporter: Misha Tyulenev Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Won't Fix Votes: 0
Labels: PM550
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding
Participants:

 Description   

Investigate if code
https://github.com/mongodb/mongo/blob/v3.2.3/src/mongo/client/parallel.cpp#L402-L419
is still used.
If it is add a method to RemoteCommandTargeter that can propagate the result ReplicaSetMonitor::isKnownToHaveGoodPrimary() method to the caller and use it in the code instead.
Net result: no dependency on ReplicaSetMonitor



 Comments   
Comment by Kaloian Manassiev [ 05/Dec/16 ]

The parallel.cpp implementation will have to change regardless as part of the Lamport clock changes and this change will either fall out of (if we switch it to use OP_COMMAND) or if we don't get to it, there is no pressing need to improve parallel.cpp.

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