summaryrefslogtreecommitdiff
path: root/jstests/sharding/remove2.js
diff options
context:
space:
mode:
authorDavid Storch <david.storch@10gen.com>2015-09-21 18:26:40 -0400
committerDavid Storch <david.storch@10gen.com>2015-09-22 14:35:12 -0400
commitb1982bb7fb610def9b23ab08b0317e6f409c1784 (patch)
tree1d2785f123e930cc5fd3e1be00239ca5deee6b78 /jstests/sharding/remove2.js
parent32e552cd97e63ca68beeef69670e27c6c19f70c2 (diff)
downloadmongo-b1982bb7fb610def9b23ab08b0317e6f409c1784.tar.gz
SERVER-20194 use the new mongos query path by default for legacy OP_QUERY/OP_GET_MORE reads
Explicitly configures yet-to-be-debugged tests to use the old mongos query path by setting useClusterClientCursor=false.
Diffstat (limited to 'jstests/sharding/remove2.js')
-rw-r--r--jstests/sharding/remove2.js3
1 files changed, 3 insertions, 0 deletions
diff --git a/jstests/sharding/remove2.js b/jstests/sharding/remove2.js
index 74f760050db..c0c622a2974 100644
--- a/jstests/sharding/remove2.js
+++ b/jstests/sharding/remove2.js
@@ -78,6 +78,9 @@ var st = new ShardingTest({ shards: {
enableBalancer: true
}});
+// TODO: SERVER-20194. This test forces use of the old mongos query path.
+assert.commandWorked(st.s.adminCommand({setParameter: 1, useClusterClientCursor: false}));
+
// Pending resolution of SERVER-8598, we need to wait for deletion after chunk migrations to avoid
// a pending delete re-creating a database after it was dropped.
st.s.getDB("config").settings.update( { _id: "balancer" },