summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEsha Maharishi <esha.maharishi@mongodb.com>2018-03-01 13:42:06 -0500
committerEsha Maharishi <esha.maharishi@mongodb.com>2018-03-01 13:44:25 -0500
commit67af2fc406b8e9118ae66fb9bb17e72a77850b83 (patch)
treea5f804289ffe0f91c852ed1492a9c5cce8e2b87d
parent9cec63d67ed2f63d26303a1c44189e1ac73d167a (diff)
downloadmongo-67af2fc406b8e9118ae66fb9bb17e72a77850b83.tar.gz
SERVER-33547 fix for split_against_shard_with_invalid_split_points.js
-rw-r--r--jstests/sharding/split_against_shard_with_invalid_split_points.js4
1 files changed, 1 insertions, 3 deletions
diff --git a/jstests/sharding/split_against_shard_with_invalid_split_points.js b/jstests/sharding/split_against_shard_with_invalid_split_points.js
index 9c1ec276e2b..5add17c87a8 100644
--- a/jstests/sharding/split_against_shard_with_invalid_split_points.js
+++ b/jstests/sharding/split_against_shard_with_invalid_split_points.js
@@ -17,8 +17,6 @@
// Try to do a split with invalid parameters through mongod
var callSplit = function(db, minKey, maxKey, splitPoints) {
var res = assert.commandWorked(st.s.adminCommand({getShardVersion: 'TestSplitDB.Coll'}));
- var shardVersion = [res.version, res.versionEpoch];
-
return db.runCommand({
splitChunk: 'TestSplitDB.Coll',
from: st.shard0.shardName,
@@ -26,7 +24,7 @@
max: maxKey,
keyPattern: {x: 1},
splitKeys: splitPoints,
- shardVersion: shardVersion,
+ epoch: res.versionEpoch,
});
};