[SERVER-6623] timing error in repl_monitor_stress.js Created: 27/Jul/12  Updated: 11/Jul/16  Resolved: 27/Jul/12

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

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

Operating System: ALL
Participants:

 Description   

Error("Printing Stack Trace")@:0
()@src/mongo/shell/utils.js:37
}, msg:undefined
("assert.soon failed: function () {\n    var connPoolStats = mongos.getDB(\"admin\").runCommand({connPoolStats:1});\n    var replView = connPoolStats.replicaSets[replTest.name];\n    print(\"Current replView: \" + tojson(replView));\n    return replView.master == node;\n}, msg:undefined")@src/mongo/shell/utils.js:58
((function () {var connPoolStats = mongos.getDB("admin").runCommand({connPoolStats:1});var replView = connPoolStats.replicaSets[replTest.name];print("Current replView: " + tojson(replView));return replView.master == node;}))@src/mongo/shell/utils.js:167
@/Users/yellow/buildslave/OS_X_105_64bit_DUR_OFF/mongo/jstests/slowNightly/repl_monitor_stress.js:52
    var connPoolStats = mongos.getDB("admin").runCommand({connPoolStats:1});
    var replView = connPoolStats.replicaSets[replTest.name];
    print("Current replView: " + tojson(replView));
    return replView.master == node;
Thu Jul 26 20:37:34 uncaught exception: assert.soon failed: function () {
failed to load: /Users/yellow/buildslave/OS_X_105_64bit_DUR_OFF/mongo/jstests/slowNightly/repl_monitor_stress.js
}, msg:undefined

http://buildlogs.mongodb.org/build/5011e284d2a60f17910000c9/test/5011e285d2a60f1415000282/
http://buildbot.mongodb.org/builders/OS%20X%2010.5%2064-bit%20DUR%20OFF



 Comments   
Comment by auto [ 27/Jul/12 ]

Author:

{u'date': u'2012-07-27T09:53:54-07:00', u'email': u'randolph@10gen.com', u'name': u'Randolph Tan'}

Message: Buildbot fix for SERVER-6623

Increase the timeouts (followed the same timeout as ReplSetTest.awaitRSClientHosts) to wait for mongos to see the replica set changes.
Branch: master
https://github.com/mongodb/mongo/commit/6d21cc3766075927544b4255af3914083724005d

Comment by Randolph Tan [ 27/Jul/12 ]

Timeline of events:

20:37:03 reconfig - current primary stepped down
20:37:24 ReplicaSetMonitorWatcher tries to refresh and can't find a primary
20:37:25 node 4 now becomes primary
20:37:34 assert soon timed out
20:37:34 ReplicaSetMonitorWatcher found the master

So the time it took for mongos to realize that the master is up was too long and the test timed out.

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