[SERVER-10437] chaining.js failed on Linux 64-bit subscription, "error doing query" Created: 05/Aug/13  Updated: 11/Jul/16  Resolved: 07/Aug/13

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

Type: Bug Priority: Major - P3
Reporter: Matt Kangas Assignee: Randolph Tan
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-10414 chaining.js timeouts on V2.4 Linux 32... Closed
Operating System: ALL
Participants:

 Description   

This fails with a different message than SERVER-10414 (not a timeout).

V2.4 Linux 64-bit Subscription Ubuntu 1204 Build #153 (August 5)

http://buildlogs.mongodb.org/V2.4%20Linux%2064-bit%20Subscription%20Ubuntu%201204/builds/153/test/replica%20sets/chaining.js

Mon Aug  5 16:50:59.555 Error: error doing query: failed at src/mongo/shell/query.js:78

V2.4 Linux 64-bit Subscription RHEL 5.7 Build #159 (August 3)

http://buildlogs.mongodb.org/V2.4%20Linux%2064-bit%20Subscription%20RHEL%205.7/builds/159/test/replica%20sets/chaining.js

Sat Aug  3 02:42:58.825 Error: error doing query: failed at src/mongo/shell/query.js:78

What actually failed here?



 Comments   
Comment by auto [ 07/Aug/13 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-10437 remove chaining.js test

It is testing functionality that has been deprecated by the new sync source updater.
Also, tags.js covers testing chaining with network failures, so there is no further
need for this test. chaining.js is racy with respect to the way it activates a
failpoint in the socket class, which was causing the test to fail sometimes.
Branch: v2.4
https://github.com/mongodb/mongo/commit/75d9c31c5c2c3a0c937a9b3adb7708c301388021

Comment by auto [ 07/Aug/13 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-10437 remove chaining.js test

It is testing functionality that has been deprecated by the new sync source updater.
Also, tags.js covers testing chaining with network failures, so there is no further
need for this test. chaining.js is racy with respect to the way it activates a
failpoint in the socket class, which was causing the test to fail sometimes.
Branch: master
https://github.com/mongodb/mongo/commit/703fbad99ac3e02c804c1dc2bd63b84f29168dea

Comment by Randolph Tan [ 06/Aug/13 ]

I believe this is the same cause for the failure in SERVER-10414 (timing issue in test) - the ticking thowSockExcep failpoint bomb. This can be demonstrated easily by activating the failpoint such that it will be surely triggered by the same thread:

var conn = MongoRunner.runMongod();
var adminDB = conn.getDB('admin');
var res = adminDB.runCommand({ configureFailPoint: 'throwSockExcep', mode: { times : 1 }});
print('res: ' + tojson(res));

The log output looks like this:

Tue Aug  6 13:59:45.304 DBClientCursor::init call() failed
Tue Aug  6 13:59:45.305 Error: error doing query: failed at src/mongo/shell/query.js:81

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