[SERVER-15966] initial_sync3.js fails sporadically due to wrong node being elected primary Created: 06/Oct/14  Updated: 19/Nov/14  Resolved: 05/Nov/14

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.8.0-rc0

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

Operating System: ALL
Participants:

 Description   

http://buildlogs.mongodb.org/MCI_linux-64/builds/121974/test/replicasets_0/initial_sync3.js

Error: assert.soon failed: function () {
    var result = nodes[1].getDB("admin").runCommand({isMaster : 1});
    printjson(result);
    return result.secondary;
}
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at Function.assert.soon (src/mongo/shell/assert.js:181:51)
    at /data/mci/shell/src/jstests/replsets/initial_sync3.js:47:8



 Comments   
Comment by Githook User [ 05/Nov/14 ]

Author:

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

Message: SERVER-15966 Make initial_sync3.js deterministic about who becomes primary
Branch: master
https://github.com/mongodb/mongo/commit/3f02fd962b26014f9fcb21e0ab91462d9fc690b6

Comment by Spencer Brody (Inactive) [ 05/Nov/14 ]

Again: https://mci.10gen.com/task/mongodb_mongo_master_linux_32_ee9a858adb7e399085975072f60a3f2d63cdda7a_14_11_05_14_35_08_replicasets_linux_32

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