diff options
author | Ian Boros <ian.boros@mongodb.com> | 2021-02-19 13:48:54 -0500 |
---|---|---|
committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2021-02-24 19:47:15 +0000 |
commit | 91bdf11ca88df82ef67cc666f3181b864ad99ec1 (patch) | |
tree | ec833c307e20d4b4418f79988cda160b137baca9 | |
parent | 46fc6fb233e85538a94dda6eea91cc2ac34cee15 (diff) | |
download | mongo-91bdf11ca88df82ef67cc666f3181b864ad99ec1.tar.gz |
SERVER-54660 make kill_pinned_cursor.js more robust
-rw-r--r-- | jstests/sharding/kill_pinned_cursor.js | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/jstests/sharding/kill_pinned_cursor.js b/jstests/sharding/kill_pinned_cursor.js index 77f174834be..d4b2586a665 100644 --- a/jstests/sharding/kill_pinned_cursor.js +++ b/jstests/sharding/kill_pinned_cursor.js @@ -28,10 +28,9 @@ const shard1DB = st.shard1.getDB(kDBName); // fail. In versions 4.4 and later, this is solved by running the dummy operation with a 'comment' // and filtering $currentOp output based based on the comment. This behavior is unavailable in // earlier versions (see SERVER-29794), so we instead disable the background job. -assert.commandWorked( - shard0DB.adminCommand({setParameter: 1, enableShardedIndexConsistencyCheck: false})); -assert.commandWorked( - shard1DB.adminCommand({setParameter: 1, enableShardedIndexConsistencyCheck: false})); +st._configServers.forEach( + config => config.adminCommand({setParameter: 1, enableShardedIndexConsistencyCheck: false})); + let coll = mongosDB.jstest_kill_pinned_cursor; coll.drop(); |