[SERVER-15228] Make awaitReplication fail with NotMaster in ReplicationCoordinatorImpl Created: 11/Sep/14  Updated: 25/Oct/14  Resolved: 01/Oct/14

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

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
related to SERVER-9617 getLastError should have a clearer er... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

We need to preserve the legacy behavior, which is:
1. check on entry if we are not primary; return NotMaster immediately
2. upon stepdown, need to signal any blocked awaitReplication() callers, so that they can wake up and return NotMaster
Note that we need to be careful to avoid any state-change races between 1 and 2.



 Comments   
Comment by Githook User [ 01/Oct/14 ]

Author:

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

Message: SERVER-15228 Make awaitReplication properly detect NotMaster conditions
Branch: master
https://github.com/mongodb/mongo/commit/1444aa92f73b878a33f0362819c6c2b780539803

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