[SERVER-10130] replsets/no_chaining.js and tags.js failing on Nightly Linux 32-bit Created: 08/Jul/13  Updated: 11/Jul/16  Resolved: 18/Nov/13

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

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Daniel Pasette (Inactive)
Resolution: Done Votes: 0
Labels: build-failure, buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

buildbot Nightly Linux RHEL 32-bit
buildbot Nightly Linux 32-bit Build #1416


Operating System: ALL
Participants:

 Description   

Builder Nightly Linux RHEL 32-bit Build #566 Mon July 08

http://buildbot.mongodb.org/builders/Nightly%20Linux%20RHEL%2032-bit/builds/566/steps/test_9/logs/stdio
http://buildlogs.mongodb.org/Nightly%20Linux%20RHEL%2032-bit/builds/566/test/replica%20sets/no_chaining.js

make sure chaining is not happening
...
assert failed : Check that 2 does not catch up
Error: Printing Stack Trace
    at printStackTrace (src/mongo/shell/utils.js:37:15)
    at doassert (src/mongo/shell/assert.js:6:5)
    at assert (src/mongo/shell/assert.js:14:5)
    at checkNoChaining (/data/buildslaves/Linux_RHEL_32bit_Nightly/mongo/jstests/replsets/no_chaining.js:44:9)
    at /data/buildslaves/Linux_RHEL_32bit_Nightly/mongo/jstests/replsets/no_chaining.js:66:5
Mon Jul  8 01:42:52.224 assert failed : Check that 2 does not catch up at src/mongo/shell/assert.js:7
failed to load: /data/buildslaves/Linux_RHEL_32bit_Nightly/mongo/jstests/replsets/no_chaining.js



 Comments   
Comment by Githook User [ 18/Nov/13 ]

Author:

{u'username': u'monkey101', u'name': u'Dan Pasette', u'email': u'dan@10gen.com'}

Message: SERVER-10130: add gle to update config call
Branch: master
https://github.com/mongodb/mongo/commit/a6db386c9b8461e1d0123ce2a13aa3bdf1d02061

Comment by Daniel Pasette (Inactive) [ 16/Nov/13 ]

This is failing fairly consistently on linux-32. The root cause looks to be a failure in mongobridge rather than in the test case. The bridges appear to be set up properly, but after the last member in the replica set is restarted, the connections from the member to the other two members bypass the bridge.

Passing test shows bridge intercepting the connection:

 m31002| 2013-11-16T01:42:40.276-0500 [initandlisten] waiting for connections on port 31002
 m31002| 2013-11-16T01:42:40.283-0500 [websvr] admin web console waiting for connections on port 32002
 m31002| 2013-11-16T01:42:40.286-0500 [rsStart] replSet I am ip-10-116-42-47:31002
 m31002| 2013-11-16T01:42:40.286-0500 [rsStart] replSet STARTUP2
 m31002| 2013-11-16T01:42:40.287-0500 [rsSync] replSet SECONDARY
==>  m31010| 2013-11-16T01:42:40.288-0500 connection accepted from 10.116.42.47:59845 #2 (1 connection now open)
 m31001| 2013-11-16T01:42:40.289-0500 [initandlisten] connection accepted from 10.116.42.47:48342 #2 (2 connections now open)
==>  m31009| 2013-11-16T01:42:40.290-0500 connection accepted from 10.116.42.47:36061 #2 (1 connection now open)
 m31000| 2013-11-16T01:42:40.291-0500 [initandlisten] connection accepted from 10.116.42.47:39812 #3 (3 connections now open)

Failng test shows connections made directly:

 m31002| 2013-11-15T18:12:40.908-0500 [initandlisten] waiting for connections on port 31002
 m31002| 2013-11-15T18:12:40.916-0500 [websvr] admin web console waiting for connections on port 32002
 m31002| 2013-11-15T18:12:40.920-0500 [rsStart] replSet I am ip-10-100-222-218:31002
 m31002| 2013-11-15T18:12:40.920-0500 [rsStart] replSet STARTUP2
 m31002| 2013-11-15T18:12:40.921-0500 [rsSync] replSet SECONDARY
==> m31001| 2013-11-15T18:12:40.922-0500 [initandlisten] connection accepted from 10.100.222.218:38676 #2 (2 connections now open)
==> m31000| 2013-11-15T18:12:40.923-0500 [initandlisten] connection accepted from 10.100.222.218:39423 #3 (3 connections now open)

Seeing this for both no_chaining.js and tags.js

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

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

Comment by Scott Hernandez (Inactive) [ 04/Nov/13 ]

Hasn't come up again and can't reproduce so closing until we get more info.

Comment by Matt Kangas [ 25/Jul/13 ]

It's baaaaack...

Nightly Linux 32-bit Build #1416 Wed July 24 revision f9b40bf3ae5

http://buildbot.mongodb.org/builders/Nightly%20Linux%2032-bit/builds/1416/steps/test_9/logs/stdio

http://buildlogs.mongodb.org/Nightly%20Linux%2032-bit/builds/1416/test/replica%20sets/no_chaining.js

Wed Jul 24 10:52:29.534 assert failed : Check that 2 does not catch up at src/mongo/shell/assert.js:7
failed to load: /mnt/slaves/Linux_32bit_Nightly/mongo/jstests/replsets/no_chaining.js

Comment by Scott Hernandez (Inactive) [ 11/Jul/13 ]

Looks to be passing now, no? http://buildbot.mongodb.org/builders/Nightly%20Linux%20RHEL%2032-bit/builds/571

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