[SERVER-15040] nodes fail to count their own votes in majority-up calculation in TopologyCoordinator Created: 26/Aug/14  Updated: 11/Jul/16  Resolved: 27/Aug/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 2.7.5
Fix Version/s: 2.7.6

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: cap-ticket-needed
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
Operating System: ALL
Participants:

 Description   

To calculate votes when checking if we can see a majority, a node checks if each member is up and then adds their votes to total if they are. However, its own HeartbeatMemberData is never set to up, so it does not count its own votes.

One solution is to special case itself in vote counting, so that its votes are always added. Another could be to set itself up when parsing a new config.



 Comments   
Comment by Githook User [ 27/Aug/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-15040 initialize our own HeartbeatMemberData when updating config in the TopologyCoordinator
Branch: master
https://github.com/mongodb/mongo/commit/32643343be6e0100a887dae4a44d33f710dfd086

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