[SERVER-15223] TopologyCoordinatorImpl should report member state RS_PRIMARY, RS_REMOVED or RS_STARTUP2 after first call to updateConfig Created: 11/Sep/14  Updated: 02/Oct/14  Resolved: 12/Sep/14

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

Type: Bug Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Participants:

 Description   

After setting a valid configuration on the topology coordinator via the updateConfig method, one of the following conditions should hold.

  1. _selfIndex == -1, and the reported state is RS_REMOVED
  2. _selfIndex == 0, the config contains exactly one member, and
    1. That member is electable, in which case the reported state should be RS_PRIMARY
    2. That member is not electable, in which case either the reported state is RS_ARBITER or RS_STARTUP2 based on the config's arbiter flag.
  3. The config contains many members, in which case the reported state is RS_STARTUP2

If the reported state is RS_STARTUP2, the applier thread will eventually promote to RS_SECONDARY, possibly after an initial sync and/or a stint in RS_RECOVERY.



 Comments   
Comment by Githook User [ 12/Sep/14 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-15223 Properly handle MemberStates before first heartbeat in TopologyCoordinatorImpl.
Branch: master
https://github.com/mongodb/mongo/commit/ce737ebed71bc4485180b86832e907d820858664

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