[SERVER-4809] Linux build failing on sharding_multiple_ns_rs.js Created: 30/Jan/12  Updated: 11/Jul/16  Resolved: 30/Jan/12

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: None
Fix Version/s: 2.1.0

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

Operating System: ALL
Participants:

 Description   

http://buildbot.mongodb.org/builders/Linux%2064-bit%20DEBUG/builds/718/steps/test/logs/stdio

 m30999| Mon Jan 30 03:16:50 [conn1] SocketException: remote: 127.0.0.1:31100 error: 9001 socket exception [0] server [127.0.0.1:31100] 
 m30999| Mon Jan 30 03:16:50 [conn1] DBClientCursor::init lazy say() failed
 m30999| Mon Jan 30 03:16:50 [conn1] DBClientCursor::init message from say() was empty
 m30999| Mon Jan 30 03:16:50 [conn1] got not master for: SERVER04:31100
 m30999| Mon Jan 30 03:16:50 [conn1] User Assertion: 15988:error querying server
 m30999| Mon Jan 30 03:16:50 [conn1] warning: db exception when finishing on blah-rs0:blah-rs0/SERVER04:31100,SERVER04:31101,SERVER04:31102, current connection state is { state: { conn: "blah-rs0/SERVER04:31100,SERVER04:31101,SERVER04:31102", vinfo: "test.foo @ 1|4", cursor: "(empty)", count: 0, done: false }, retryNext: false, init: true, finish: true, errored: false } :: caused by :: 15988 error querying server
 m30999| Mon Jan 30 03:16:50 [conn1] AssertionException while processing op type : 2004 to : test.foo :: caused by :: 15988 error querying server
Mon Jan 30 03:16:50 uncaught exception: error { "$err" : "error querying server", "code" : 15988 }
failed to load: /home/yellow/buildslave/Linux_64bit_DEBUG/mongo/jstests/slowNightly/sharding_multiple_ns_rs.js



 Comments   
Comment by auto [ 30/Jan/12 ]

Author:

{u'login': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}

Message: SERVER-4809 buildbot sharding_multiple_ns_rs.js sometimes rs election can take longer, need to wait for election and mongos detection
Branch: master
https://github.com/mongodb/mongo/commit/b9a602fa7c5e7b3f14825a4b7ccf0381fd6fb864

Comment by Greg Studer [ 30/Jan/12 ]

Think the issue here was that the master took a long time to get elected, about 20s, so there was no time for mongos to detect the change given the wait time of 20s in the test.

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