[SERVER-4280] sharding/sync3.js failure when run with auth Created: 14/Nov/11  Updated: 11/Jul/16  Resolved: 22/Nov/11

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

Type: Bug Priority: Major - P3
Reporter: Kristina Chodorow (Inactive) Assignee: Spencer Brody (Inactive)
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-4237 Enable the full js test suite to run ... Closed
Operating System: ALL
Participants:

 Comments   
Comment by Spencer Brody (Inactive) [ 22/Nov/11 ]

We don't need to be able to create direct SyncClusterConnections to standalone mongod's that aren't config servers when using auth, so it's okay that this test is failing.

Comment by Spencer Brody (Inactive) [ 22/Nov/11 ]

Committed 220776dff8d5a1de1ceb5e98691122822fe65c76: Skip failing SyncClusterConnection tests when running tests with auth

Comment by Spencer Brody (Inactive) [ 22/Nov/11 ]

Managed to reproduce the stack trace by testing manually. Investigating further now.

Comment by Spencer Brody (Inactive) [ 22/Nov/11 ]

I'm not getting a stack trace like that. @kristina, how did you run the test?

All I'm seeing is:

Tue Nov 22 15:06:55 DBClientCursor::init call() failed
Tue Nov 22 15:06:55 query failed : admin.$cmd { _testDistLockWithSyncCluster: 1.0, host: "localhost:30000,localhost:30001,localhost:30002" } to: 127.0.0.1:30000
Tue Nov 22 15:06:55 Error: error doing query: failed shell/collection.js:155
failed to load: /ssd/mongo/jstests/sharding/sync3.js

Comment by Kristina Chodorow (Inactive) [ 14/Nov/11 ]

sync6.js seems to have a distlock bug, too, skewed threads aren't incremented correctly.

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