[SERVER-18] pair3.js test fails due to one server remaining in negotiating (-1) state instead of moving to can't arb (-3) state Created: 15/Apr/09  Updated: 26/Sep/15  Resolved: 19/May/09

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

Type: Bug Priority: Minor - P4
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-16841 rollback could exhaust all free file ... Closed
Participants:

 Description   

<http://buildbot.mongodb.org/builders/Linux%2064-bit/builds/76/steps/test_3/logs/stdio>

ismaster:

{"ismaster" : -1 , "remote" : "127.0.0.1:39764" , "ok" : 1}

ismaster:

{"ismaster" : -3 , "remote" : "127.0.0.1:53868" , "info" : "can't connect to arb" , "ok" : 1}

ismaster:

{"ismaster" : -1 , "remote" : "127.0.0.1:39764" , "ok" : 1}

(mongo init):708 assert.soon failed: function ()

{ lm = ismaster( l ); rm = ismaster( r ); assert( lm == -1 || lm == -3, "lm value invalid" ); assert( rm == -1 || rm == -3, "rm value invalid" ); return ( lm == -3 && rm == -3 ); }

throw "assert.soon failed: " + f;



 Comments   
Comment by Aaron Staple [ 19/May/09 ]

This test has been completely rewritten.

Comment by Aaron Staple [ 30/Apr/09 ]

I added some logging to help debug if this happens again.

Generated at Thu Feb 08 02:52:49 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.