[SERVER-9311] replsetprio1.js failing consistently on Solaris in v2.4 branch Created: 10/Apr/13  Updated: 10/Dec/14  Resolved: 11/Apr/13

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

Type: Bug Priority: Critical - P2
Reporter: Ian Whalen (Inactive) Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-4836 Making replica set sync ups faster wi... Closed
Operating System: ALL
Participants:

 Description   

http://buildlogs.mongodb.org/V2.4%20Solaris-SmartOS%2064-bit/builds/35/test/replica%20sets/replsetprio1.js
http://buildlogs.mongodb.org/V2.4%20Solaris-SmartOS%2064-bit/builds/34/test/replica%20sets/replsetprio1.js

	
ReplSetTest getMaster failed: "[Finding master] timed out after 60000ms ( 31 tries )"
Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:37:7)
    at ReplSetTest.getMaster (src/mongo/shell/replsettest.js:412:1)
    at ReplSetTest.awaitSecondaryNodes (src/mongo/shell/replsettest.js:383:6)
    at ReplSetTest.initiate (src/mongo/shell/replsettest.js:482:6)
    at doTest (/data/buildslaves/SolarisSmartOS_64bit_V2.4/mongo/jstests/replsets/replsetprio1.js:9:14)
    at /data/buildslaves/SolarisSmartOS_64bit_V2.4/mongo/jstests/replsets/replsetprio1.js:60:1
Wed Apr 10 04:28:40.763 JavaScript execution failed: [Finding master] timed out after 60000ms ( 31 tries ) at src/mongo/shell/replsettest.js:L413



 Comments   
Comment by Eric Milkie [ 11/Apr/13 ]

This will be helped by backporting my replset startup efficiency change into 2.4.3

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