Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-66225

Catalog shard incompatible with tests using arbiters

    • Sharding NYC
    • 3

      [js_test:arbiters_do_not_use_cluster_time] 2022-05-04T22:34:22.319Z assert: command failed: {
      [js_test:arbiters_do_not_use_cluster_time] 	"ok" : 0,
      [js_test:arbiters_do_not_use_cluster_time] 	"hosts" : [
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20020",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20021",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20022",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20023",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20024"
      [js_test:arbiters_do_not_use_cluster_time] 	],
      [js_test:arbiters_do_not_use_cluster_time] 	"name" : "arbiters_do_not_use_cluster_time-rs0",
      [js_test:arbiters_do_not_use_cluster_time] 	"error" : "Error: assert.soon failed, msg : reconfig for fixture set up failed The hang analyzer is automatically called in assert.soon functions. If you are *expecting* assert.soon to possibly fail, call assert.soon with {runHangAnalyzer: false} as the fifth argument (you can fill unused arguments with `undefined`).",
      [js_test:arbiters_do_not_use_cluster_time] 	"stack" : "doassert@src/mongo/shell/assert.js:20:14\nassert.soon@src/mongo/shell/assert.js:382:25\nReplSetTest/this.initiateWithAnyNodeAsPrimary@src/mongo/shell/replsettest.js:1544:24\n@eval:2:13\n@eval:4:43\n_threadStartWrapper@:26:28\n"
      [js_test:arbiters_do_not_use_cluster_time] } : Initiating shard or config servers as a replica set failed
      [js_test:arbiters_do_not_use_cluster_time] _getErrorWithCode@src/mongo/shell/utils.js:24:13
      [js_test:arbiters_do_not_use_cluster_time] doassert@src/mongo/shell/assert.js:18:14
      [js_test:arbiters_do_not_use_cluster_time] _assertCommandWorked@src/mongo/shell/assert.js:760:25
      [js_test:arbiters_do_not_use_cluster_time] assert.commandWorked@src/mongo/shell/assert.js:852:16
      [js_test:arbiters_do_not_use_cluster_time] ShardingTest/<@src/mongo/shell/shardingtest.js:1518:24
      [js_test:arbiters_do_not_use_cluster_time] ShardingTest@src/mongo/shell/shardingtest.js:1517:24
      [js_test:arbiters_do_not_use_cluster_time] @jstests/sharding/arbiters_do_not_use_cluster_time.js:7:10
      [js_test:arbiters_do_not_use_cluster_time] @jstests/sharding/arbiters_do_not_use_cluster_time.js:42:3
      [js_test:arbiters_do_not_use_cluster_time] uncaught exception: Error: command failed: {
      [js_test:arbiters_do_not_use_cluster_time] 	"ok" : 0,
      [js_test:arbiters_do_not_use_cluster_time] 	"hosts" : [
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20020",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20021",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20022",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20023",
      [js_test:arbiters_do_not_use_cluster_time] 		"127.0.0.1:20024"
      [js_test:arbiters_do_not_use_cluster_time] 	],
      [js_test:arbiters_do_not_use_cluster_time] 	"name" : "arbiters_do_not_use_cluster_time-rs0",
      [js_test:arbiters_do_not_use_cluster_time] 	"error" : "Error: assert.soon failed, msg : reconfig for fixture set up failed The hang analyzer is automatically called in assert.soon functions. If you are *expecting* assert.soon to possibly fail, call assert.soon with {runHangAnalyzer: false} as the fifth argument (you can fill unused arguments with `undefined`).",
      [js_test:arbiters_do_not_use_cluster_time] 	"stack" : "doassert@src/mongo/shell/assert.js:20:14\nassert.soon@src/mongo/shell/assert.js:382:25\nReplSetTest/this.initiateWithAnyNodeAsPrimary@src/mongo/shell/replsettest.js:1544:24\n@eval:2:13\n@eval:4:43\n_threadStartWrapper@:26:28\n"
      [js_test:arbiters_do_not_use_cluster_time] } : Initiating shard or config servers as a replica set failed :
      [js_test:arbiters_do_not_use_cluster_time] _getErrorWithCode@src/mongo/shell/utils.js:24:13
      [js_test:arbiters_do_not_use_cluster_time] doassert@src/mongo/shell/assert.js:18:14
      [js_test:arbiters_do_not_use_cluster_time] _assertCommandWorked@src/mongo/shell/assert.js:760:25
      [js_test:arbiters_do_not_use_cluster_time] assert.commandWorked@src/mongo/shell/assert.js:852:16
      [js_test:arbiters_do_not_use_cluster_time] ShardingTest/<@src/mongo/shell/shardingtest.js:1518:24
      [js_test:arbiters_do_not_use_cluster_time] ShardingTest@src/mongo/shell/shardingtest.js:1517:24
      [js_test:arbiters_do_not_use_cluster_time] @jstests/sharding/arbiters_do_not_use_cluster_time.js:7:10
      [js_test:arbiters_do_not_use_cluster_time] @jstests/sharding/arbiters_do_not_use_cluster_time.js:42:3
      [js_test:arbiters_do_not_use_cluster_time] failed to load: jstests/sharding/arbiters_do_not_use_cluster_time.js
      
      

            Assignee:
            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: