[SERVER-5886] initial_sync3.js bb failure with "not master" Created: 21/May/12  Updated: 11/Jul/16  Resolved: 21/May/12

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

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

Issue Links:
Duplicate
is duplicated by SERVER-5884 uncaught exception: [Finding master] ... Closed
Operating System: ALL
Participants:

 Description   

http://buildbot.mongodb.org/builders/Linux%2032-bit%20debug/builds/1747/steps/test_7/logs/stdio



 Comments   
Comment by auto [ 21/May/12 ]

Author:

{u'login': u'kchodorow', u'name': u'Kristina', u'email': u'kristina@10gen.com'}

Message: Catch errors on stepdown SERVER-5886

If the exception is not caught, the manager will short-circuit and
never unset primary-ship (if the former primary is down). Because
the short-circuiting node thinks that the down node is still
primary, it will veto any other election.
Branch: master
https://github.com/mongodb/mongo/commit/489bc6a6766460b4d625db5f429c28cf9fbcaf28

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