[SERVER-7359] timeout in repl_monitor_stress.js waiting for node to become master Created: 15/Oct/12  Updated: 21/Mar/13  Resolved: 21/Mar/13

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

Type: Bug Priority: Blocker - P1
Reporter: Ian Whalen (Inactive) Assignee: Unassigned
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File repl_monitor_stress.txt    
Operating System: ALL
Participants:

 Description   

http://buildlogs.mongodb.org/V2.2%20Linux%2064-bit%20Legacy/builds/62/test/slow%20nightly/repl_monitor_stress.js

	
Mon Oct 15 07:50:48 uncaught exception: assert.soon failed: function () {
    var connPoolStats = mongos.getDB("admin").runCommand({connPoolStats:1});
    var replView = connPoolStats.replicaSets[replTest.name];
    print("Current replView: " + tojson(replView));
    return replView.master == node;
}, msg:timed out waiting for node " + node + " to become master
failed to load: /mnt/data/slaves/Linux_64bit_Legacy_V2.2/mongo/jstests/slowNightly/repl_monitor_stress.js



 Comments   
Comment by Ian Whalen (Inactive) [ 21/Mar/13 ]

this is probably unrelated - the correct ticket related to the current failure is SERVER-7867

Comment by Ian Whalen (Inactive) [ 21/Mar/13 ]

I'm now seeing identical error messages consistently on the Windows 64 build on the 2.2 branch:

http://buildlogs.mongodb.org/V2.2%20Windows%2064-bit/builds/234/test/slow%20nightly/repl_monitor_stress.js

Wed Mar 20 23:44:37 uncaught exception: assert.soon failed: function () {
    var connPoolStats = mongos.getDB("admin").runCommand({connPoolStats:1});
    var replView = connPoolStats.replicaSets[replTest.name];
    print("Current replView: " + tojson(replView));
    return replView.master == node;
}, msg:timed out waiting for node " + node + " to become master
failed to load: D:\slave\Windows_64bit_V2.2\mongo\jstests\slowNightly\repl_monitor_stress.js

Comment by Randolph Tan [ 17/Oct/12 ]

Based from the logs, the node that was intended to become primary during the test setup did not become the priority despite having the highest priority. This synchronization step would become unnecessary when ported to the cpp unit test using the mock clients.

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