From 553dff7f3b96b95883b406c7486a04877fbfb094 Mon Sep 17 00:00:00 2001 From: Eddie Louie Date: Tue, 17 Oct 2017 15:47:56 -0400 Subject: SERVER-31579 Tag specific sharding tests as being resource intensive --- jstests/sharding/move_chunk_wc.js | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) (limited to 'jstests/sharding/move_chunk_wc.js') diff --git a/jstests/sharding/move_chunk_wc.js b/jstests/sharding/move_chunk_wc.js index 85ae3400652..0cc8c163b6e 100644 --- a/jstests/sharding/move_chunk_wc.js +++ b/jstests/sharding/move_chunk_wc.js @@ -1,5 +1,3 @@ -load('jstests/libs/write_concern_util.js'); - /** * This commands tests that moveChunk gives a proper response when the writeConcern cannot be met. * The test creates a sharded cluster with shards and config servers of different sizes to see how @@ -8,7 +6,12 @@ load('jstests/libs/write_concern_util.js'); * It then passes a writeConcern too high for the to shard and sees that it fails. It then passes * a writeConcern too high for the from shard and sees that that fails. moveChunk does not yield * a writeConcernError. It should simply fail when the writeConcern is not met on the shards. + * + * This test is labeled resource intensive because its total io_write is 617MB compared to a median + * of 135MB across all sharding tests in mmapv1. + * @tags: [resource_intensive] */ +load('jstests/libs/write_concern_util.js'); (function() { "use strict"; -- cgit v1.2.1