[SERVER-17998] Ignore socket exceptions in initial_sync_unsupported_auth_schema.js test Created: 10/Apr/15  Updated: 19/Sep/15  Resolved: 13/Apr/15

Status: Closed
Project: Core Server
Component/s: Testing Infrastructure
Affects Version/s: 3.1.1
Fix Version/s: 3.0.3, 3.1.2

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

Issue Links:
Related
is related to SERVER-17808 Ensure availability in initial_sync_u... Closed
is related to SERVER-17826 Ignore ismaster exceptions in initial... Closed
is related to SERVER-17671 Refuse to complete initial sync from ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Sprint: Sharding 2 04/24/15
Participants:

 Description   

The regression test for SERVER-17671 (initial_sync_unsupported_auth_schema.js) can fail if cluster reinitialization coincides with the new node aborting. The solution is to ignore socket exceptions in addition to the already ignored query errors.

Patch build failure from a windows-64-2k8-debug host:

2015-04-10T19:03:32.422+0000 I NETWORK  Socket say send() errno:10054 An existing connection was forcibly closed by the remote host. 127.0.0.1:31002
2015-04-10T19:03:32.433+0000 E QUERY    Error: socket exception [SEND_ERROR] for 127.0.0.1:31002
    at DBQuery._exec (src/mongo/shell/query.js:102:40)
    at DBQuery.hasNext (src/mongo/shell/query.js:250:10)
    at DBCollection.findOne (src/mongo/shell/collection.js:188:19)
    at DB.runCommand (src/mongo/shell/db.js:58:41)
    at src/mongo/shell/replsettest.js:358:55
    at Function.assert.soon (src/mongo/shell/assert.js:183:17)
    at ReplSetTest.awaitSecondaryNodes (src/mongo/shell/replsettest.js:351:10)
    at ReplSetTest.initiate (src/mongo/shell/replsettest.js:460:10)
    at ReplSetTest.reInitiate (src/mongo/shell/replsettest.js:475:10)
    at testInitialSyncAbortsWithUnsupportedAuthSchema (C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js:24:13)
    at C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js:92:1 at C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js:30
failed to load: C:\data\mci\shell\src\jstests\replsets\initial_sync_unsupported_auth_schema.js



 Comments   
Comment by Githook User [ 20/Apr/15 ]

Author:

{u'username': u'kkmongo', u'name': u'Kamran Khan', u'email': u'kamran.khan@mongodb.com'}

Message: SERVER-17998 Ignore socket exceptions in initial_sync_unsupported_auth_schema.js

A socket exception can legitimately occur if the added node aborts while an
ismaster command is running.

Closes #952

Signed-off-by: Ramon Fernandez <ramon.fernandez@mongodb.com>
(cherry picked from commit 0c0b19ded8a622adc089209334a6f9364a1ce543)
Branch: v3.0
https://github.com/mongodb/mongo/commit/d139a70ce0142cc1cc01f699a6006d2b2d695346

Comment by Githook User [ 13/Apr/15 ]

Author:

{u'username': u'kkmongo', u'name': u'Kamran Khan', u'email': u'kamran.khan@mongodb.com'}

Message: SERVER-17998 Ignore socket exceptions in initial_sync_unsupported_auth_schema.js

A socket exception can legitimately occur if the added node aborts while an
ismaster command is running.

Closes #952

Signed-off-by: Ramon Fernandez <ramon.fernandez@mongodb.com>
Branch: master
https://github.com/mongodb/mongo/commit/0c0b19ded8a622adc089209334a6f9364a1ce543

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