|
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.
|
|
Committed 220776dff8d5a1de1ceb5e98691122822fe65c76: Skip failing SyncClusterConnection tests when running tests with auth
|
|
Managed to reproduce the stack trace by testing manually. Investigating further now.
|
|
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
|
|
|
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.