[SERVER-65659] Fix mongobridge compatibility with catalog shard tests Created: 14/Apr/22  Updated: 27/Oct/23  Resolved: 09/Feb/23

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

Type: Task Priority: Major - P3
Reporter: Andrew Shuvalov (Inactive) Assignee: [DO NOT USE] Backlog - Sharding NYC
Resolution: Gone away Votes: 0
Labels: sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding NYC
Participants:
Story Points: 3

 Description   

Tests to reproduce - any test using mongobridge, e.g.:

jstests/sharding/advance_logical_time_with_valid_signature.js

Failure:

[js_test:advance_logical_time_with_valid_signature] assert failed : mongobridge failed to start on port 20060 13366
[js_test:advance_logical_time_with_valid_signature] doassert@src/mongo/shell/assert.js:20:14
[js_test:advance_logical_time_with_valid_signature] assert@src/mongo/shell/assert.js:151:17
[js_test:advance_logical_time_with_valid_signature] connectToBridge@src/mongo/shell/bridge.js:103:15
[js_test:advance_logical_time_with_valid_signature] ReplSetTest/this._waitForInitialConnection@src/mongo/shell/replsettest.js:2707:27
[js_test:advance_logical_time_with_valid_signature] ReplSetTest/this.startSetAwait@src/mongo/shell/replsettest.js:721:18
[js_test:advance_logical_time_with_valid_signature] ShardingTest@src/mongo/shell/shardingtest.js:1363:19
[js_test:advance_logical_time_with_valid_signature] @jstests/sharding/advance_logical_time_with_valid_signature.js:9:10
[js_test:advance_logical_time_with_valid_signature] @jstests/sharding/advance_logical_time_with_valid_signature.js:44:3
[js_test:advance_logical_time_with_valid_signature] uncaught exception: Error: assert failed : mongobridge failed to start on port 20060 :
[js_test:advance_logical_time_with_valid_signature] doassert@src/mongo/shell/assert.js:20:14
[js_test:advance_logical_time_with_valid_signature] assert@src/mongo/shell/assert.js:151:17
[js_test:advance_logical_time_with_valid_signature] connectToBridge@src/mongo/shell/bridge.js:103:15
[js_test:advance_logical_time_with_valid_signature] ReplSetTest/this._waitForInitialConnection@src/mongo/shell/replsettest.js:2707:27
[js_test:advance_logical_time_with_valid_signature] ReplSetTest/this.startSetAwait@src/mongo/shell/replsettest.js:721:18
[js_test:advance_logical_time_with_valid_signature] ShardingTest@src/mongo/shell/shardingtest.js:1363:19
[js_test:advance_logical_time_with_valid_signature] @jstests/sharding/advance_logical_time_with_valid_signature.js:9:10
[js_test:advance_logical_time_with_valid_signature] @jstests/sharding/advance_logical_time_with_valid_signature.js:44:3
[js_test:advance_logical_time_with_valid_signature]  13366
[js_test:advance_logical_time_with_valid_signature] failed to load: jstests/sharding/advance_logical_time_with_valid_signature.js



 Comments   
Comment by Jack Mulrow [ 09/Feb/23 ]

This was likely an issue with the POC implementation and hasn't come up since, so closing as gone away.

Comment by Andrew Witten (Inactive) [ 04/May/22 ]

When I run

python3 buildscripts/resmoke.py run jstests/sharding/advance_logical_time_with_valid_signature.js  --catalogShard=any --suites=sharding

I don't get the error " assert failed : mongobridge failed to start on port" but the test never finishes.

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