[SERVER-15442] server6733.js Failing Created: 23/Apr/14  Updated: 11/Jul/16  Resolved: 29/Sep/14

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

Type: Bug Priority: Major - P3
Reporter: Matt Dannenberg Assignee: Matt Dannenberg
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-13582 jstests/noPassthrough/server6733.js c... Closed
Operating System: ALL
Participants:

 Description   

Seems to be an intermittent failure. The root cause may be: SERVER-13582

https://mci.10gen.com/ui/task/mongodb_mongo_master_solaris_64_bit_1be16d8968c6bf39f01c4b3e98f854571a337823_14_04_22_19_04_07_noPassthrough_solaris_64_bit

assert.soon failed: function () {
        return A.runCommand({replSetGetStatus : 1}).syncingTo == bAddress;
    }, msg:undefined
Error: assert.soon failed: function () {
        return A.runCommand({replSetGetStatus : 1}).syncingTo == bAddress;
    }, msg:undefined
    at Error (<anonymous>)
    at doassert (src/mongo/shell/assert.js:11:14)
    at Function.assert.soon (src/mongo/shell/assert.js:180:60)
    at /data/mci/shell/mongodb-mongo-master/jstests/noPassthrough/server6733.js:33:8
2014-04-22T22:11:11.771+0000 Error: assert.soon failed: function () {
        return A.runCommand({replSetGetStatus : 1}).syncingTo == bAddress;
    }, msg:undefined at src/mongo/shell/assert.js:13
failed to load: /data/mci/shell/mongodb-mongo-master/jstests/noPassthrough/server6733.js



 Comments   
Comment by Githook User [ 29/Sep/14 ]

Author:

{u'username': u'dannenberg', u'name': u'matt dannenberg', u'email': u'matt.dannenberg@10gen.com'}

Message: SERVER-15442 fix server6733.js
Branch: master
https://github.com/mongodb/mongo/commit/481467e24fe3f42672d8bbdac7e6f46ffcd0089f

Comment by Matt Kangas [ 29/Sep/14 ]

Sorry Matt, I think this just happened again.

MCI: 96b6471266 / Windows 64-bit 2008R2+ DEBUG / noPassthrough
http://buildlogs.mongodb.org/MCI_windows-64-2k8-debug/builds/96932/test/noPassthrough_0/server6733.js

Force A to sync from B
 m31001| 2014-09-27T22:25:39.725+0000 W REPLSETS attempting to sync from WIN-EBLNSPIURRG:31002, but its latest opTime is 0 and ours is 1411856738 so this may not work
Black-hole B
Check that A switches sync targets after 30 seconds
2014-09-27 18:25:42 EDT	
 m31001| 2014-09-27T22:25:42.999+0000 I NETWORK  [conn4] end connection 172.16.22.22:53150 (2 connections now open)
 m31001| 2014-09-27T22:25:43.000+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53190 #11 (3 connections now open)
 m31000| 2014-09-27T22:25:45.055+0000 I NETWORK  [conn3] end connection 172.16.22.22:53158 (4 connections now open)
 m31000| 2014-09-27T22:25:45.056+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53191 #24 (5 connections now open)
 m31000| 2014-09-27T22:25:45.534+0000 I NETWORK  [conn9] end connection 172.16.22.22:53167 (4 connections now open)
 m31000| 2014-09-27T22:25:45.536+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53192 #25 (5 connections now open)
 m31002| 2014-09-27T22:25:57.004+0000 I NETWORK  [conn4] end connection 172.16.22.22:53152 (4 connections now open)
 m31002| 2014-09-27T22:25:57.006+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53194 #12 (5 connections now open)
 m31001| 2014-09-27T22:25:59.057+0000 I NETWORK  [conn10] end connection 172.16.22.22:53174 (2 connections now open)
 m31001| 2014-09-27T22:25:59.059+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53197 #12 (3 connections now open)
 m31002| 2014-09-27T22:25:59.540+0000 I NETWORK  [conn9] end connection 172.16.22.22:53175 (4 connections now open)
 m31002| 2014-09-27T22:25:59.540+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53198 #13 (5 connections now open)
 m31001| 2014-09-27T22:26:10.041+0000 I NETWORK  [rsBackgroundSync] Socket recv() timeout  172.16.22.22:31002
 m31001| 2014-09-27T22:26:10.041+0000 I NETWORK  [rsBackgroundSync] SocketException: remote: 172.16.22.22:31002 error: 9001 socket exception [RECV_TIMEOUT] server [172.16.22.22:31002] 
 m31001| 2014-09-27T22:26:10.042+0000 I REPLSETS [rsBackgroundSync] replSet sync source problem: 10278 dbclient error communicating with server: WIN-EBLNSPIURRG:31002
 m31001| 2014-09-27T22:26:10.042+0000 I REPLSETS [rsBackgroundSync] replSet syncing to: WIN-EBLNSPIURRG:31002 by request
 m31002| 2014-09-27T22:26:10.043+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53200 #14 (6 connections now open)
 m31001| 2014-09-27T22:26:13.013+0000 I NETWORK  [conn11] end connection 172.16.22.22:53190 (2 connections now open)
 m31001| 2014-09-27T22:26:13.017+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53202 #13 (3 connections now open)
 m31000| 2014-09-27T22:26:15.058+0000 I NETWORK  [conn24] end connection 172.16.22.22:53191 (4 connections now open)
 m31000| 2014-09-27T22:26:15.059+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53203 #26 (5 connections now open)
 m31000| 2014-09-27T22:26:15.545+0000 I NETWORK  [conn25] end connection 172.16.22.22:53192 (4 connections now open)
 m31000| 2014-09-27T22:26:15.546+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53204 #27 (5 connections now open)
 m31002| 2014-09-27T22:26:27.017+0000 I NETWORK  [conn12] end connection 172.16.22.22:53194 (5 connections now open)
 m31002| 2014-09-27T22:26:27.019+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53206 #15 (6 connections now open)
 m31001| 2014-09-27T22:26:29.069+0000 I NETWORK  [conn12] end connection 172.16.22.22:53197 (2 connections now open)
 m31001| 2014-09-27T22:26:29.071+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53209 #14 (3 connections now open)
 m31002| 2014-09-27T22:26:29.546+0000 I NETWORK  [conn13] end connection 172.16.22.22:53198 (5 connections now open)
 m31002| 2014-09-27T22:26:29.548+0000 I NETWORK  [initandlisten] connection accepted from 172.16.22.22:53210 #16 (6 connections now open)
2014-09-27 18:26:39 EDT	
assert.soon failed: function () {
        return A.runCommand({replSetGetStatus : 1}).syncingTo === primaryAddress;
    }

Comment by Ernie Hershey [ 05/May/14 ]

I think I just saw this in 2.6.1 -

https://mci.10gen.com/ui/task/mongodb_mongo_v2.6_solaris_64_bit_4b95b086d2374bdcfcdf2249272fb552c9c726e8_14_05_05_02_34_06_noPassthrough_solaris_64_bit

Comment by Matt Dannenberg [ 02/May/14 ]

should be fixed by: https://github.com/mongodb/mongo/commit/b32f849719c97dc9c73b22178329d4dda7ad1dd6

Comment by David Storch [ 01/May/14 ]

d747c572cb Solaris 64-bit noPassthrough

https://mci.10gen.com/ui/task/mongodb_mongo_master_solaris_64_bit_d747c572cbb9b6d39a64ccdc39dbb6de79c7c654_14_04_30_15_02_13_noPassthrough_solaris_64_bit

Comment by Spencer Brody (Inactive) [ 29/Apr/14 ]

https://mci.10gen.com/ui/task/mongodb_mongo_master_solaris_64_bit_bd1a02385378ee50a33db7c255217c050cc74192_14_04_28_20_02_06_noPassthrough_solaris_64_bit

Comment by Spencer Brody (Inactive) [ 25/Apr/14 ]

Another failure: https://mci.10gen.com/ui/task/mongodb_mongo_master_solaris_64_bit_f7797f6db6eaf0e3e6be0cdddca6fdf9b6c2d1dc_14_04_24_21_27_07_noPassthrough_solaris_64_bit

Comment by Matt Dannenberg [ 24/Apr/14 ]

the fix i original tried caused the other assert soon to fail

maybe that again but with a delay between command and checking result, so that we dont have a bunch of ReplSetSyncFroms queued up causing the latter assert to fail

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