[SERVER-19403] Provide feedback to RemoteCommandTargeter on NotMaster errors Created: 14/Jul/15  Updated: 25/Jan/17  Resolved: 28/Jul/15

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-19404 Ensure that all places using RemoteCo... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 7 08/10/15
Participants:

 Description   

Everywhere that uses the RemoteCommandTargeter to talk to replica sets for PrimaryOnly operations needs to be prepared to receive a NotMaster response. Currently DBClientReplicaSet feeds information back into the ReplicaSetMonitor when it receives NotMaster responses so the monitor knows to refresh its view of the who the current primary is. We need to duplicate this logic when using the RemoteCommandTargeter.



 Comments   
Comment by Githook User [ 28/Jul/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-19403 Notify targeter of NotMaster errors
Branch: master
https://github.com/mongodb/mongo/commit/789a8e2669c38ad5ebcbd07bff98d14d7354e421

Comment by Githook User [ 28/Jul/15 ]

Author:

{u'username': u'stbrody', u'name': u'Spencer T Brody', u'email': u'spencer@mongodb.com'}

Message: SERVER-19403 Notify targeter of NotMaster errors
Branch: master
https://github.com/mongodb/mongo/commit/789a8e2669c38ad5ebcbd07bff98d14d7354e421

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