[SERVER-31] in pair1.js test left node never becomes master after right node gets sigkill Created: 24/Apr/09  Updated: 12/Jul/16  Resolved: 30/Apr/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: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

Looks like the left node didn't finish its initial sync – should implement a way to wait for left's initial sync in db / test

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

m50011| replMain: sleep 3 before next pass
m50011| Thu Apr 23 22:59:27 pull: main@127.0.0.1:53444
m50011| Thu Apr 23 22:59:27 pull: cantconn couldn't connect to server 127.0.0.1:53444 127.0.0.1:53444
m34618| Thu Apr 23 22:59:27 connection accepted from 127.0.0.1:30424
m34618| Thu Apr 23 22:59:27 end connection 127.0.0.1:30424
(mongo init):710 assert.soon failed: function ()

{ lm = ismaster( l ); assert( lm == 0 || lm == 1, "lm value invalid" ); return ( lm == 1 ); }

, msg:undefined
throw "assert.soon failed: " + f + ", msg:" + msg;
^



 Comments   
Comment by Aaron Staple [ 30/Apr/09 ]

New pairing test fwk checks initial sync, so this failure shouldn't recur.

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