summaryrefslogtreecommitdiff
path: root/jstests/sharding/limit_push.js
diff options
context:
space:
mode:
authorKaloian Manassiev <kaloian.manassiev@mongodb.com>2015-10-22 11:18:50 -0400
committerKaloian Manassiev <kaloian.manassiev@mongodb.com>2015-10-23 09:50:35 -0400
commit3db9d1338c4d15b9b937516676645fd26d5f0a23 (patch)
tree639f8de38537f721aeeeb4c2eb804e9212428d65 /jstests/sharding/limit_push.js
parentc48ff0ba613fdafd51d26f664371522837809a9d (diff)
downloadmongo-3db9d1338c4d15b9b937516676645fd26d5f0a23.tar.gz
SERVER-21009 Remove usages of the multi-argument ShardingTest constructor
No functional changes, just converting everything to use the JSON-based constructor. Also moves some sharding-specific tests out of noPassthroughWithMongod and under the sharding suite.
Diffstat (limited to 'jstests/sharding/limit_push.js')
-rw-r--r--jstests/sharding/limit_push.js11
1 files changed, 5 insertions, 6 deletions
diff --git a/jstests/sharding/limit_push.js b/jstests/sharding/limit_push.js
index 5aa9bd5bee0..53acb6583eb 100644
--- a/jstests/sharding/limit_push.js
+++ b/jstests/sharding/limit_push.js
@@ -1,12 +1,9 @@
// This test is to ensure that limit() clauses are pushed down to the shards and evaluated
// See: http://jira.mongodb.org/browse/SERVER-1896
+(function() {
-s = new ShardingTest( "limit_push", 2, 1, 1 );
-
-// Stop balancer since we do manual moves.
-s.stopBalancer();
-
-db = s.getDB( "test" );
+var s = new ShardingTest({ name: "limit_push", shards: 2, mongos: 1 });
+var db = s.getDB( "test" );
// Create some data
for (i=0; i < 100; i++) { db.limit_push.insert({ _id : i, x: i}); }
@@ -50,3 +47,5 @@ for (var j in execStages.shards) {
}
s.stop();
+
+})();