summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMathias Stearn <mathias@10gen.com>2015-05-27 12:53:52 -0400
committerDan Pasette <dan@mongodb.com>2015-08-08 23:56:12 -0400
commite8668374eeefc844167e9c5fa1981ace9c6d2b10 (patch)
tree4578dc281452a9af64a25695d3dcf05bef43b22d
parent13de7c501812e3f144097cd1d62f2b955a46f523 (diff)
downloadmongo-e8668374eeefc844167e9c5fa1981ace9c6d2b10.tar.gz
Fix apitest_dbcollection.js when running in sharded passthrough
(cherry picked from commit 09569759b200b342bd99d08f262fe10ee0644427)
-rw-r--r--jstests/core/apitest_dbcollection.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/jstests/core/apitest_dbcollection.js b/jstests/core/apitest_dbcollection.js
index 6d405e8c716..765c4e186b0 100644
--- a/jstests/core/apitest_dbcollection.js
+++ b/jstests/core/apitest_dbcollection.js
@@ -249,7 +249,7 @@ assert(db.getCollection( "test_db" ).getIndexes().length == 0,24);
assert.neq(undefined, t.totalIndexSize(),
'db.collection.totalIndexSize() cannot be undefined on a non-empty collection');
- if (db.serverStatus().storageEngine.name === 'mmapv1') {
+ if (db.isMaster().msg !== 'isdbgrid' && db.serverStatus().storageEngine.name === 'mmapv1') {
// Only in MMAPv1 do we guarantee that storageSize only changes when you write to a
// collection.
assert.eq(stats.storageSize, t.storageSize());