summaryrefslogtreecommitdiff
path: root/jstests/sharding/read_pref.js
diff options
context:
space:
mode:
authorEddie Louie <eddie.louie@mongodb.com>2017-10-17 15:47:56 -0400
committerEddie Louie <eddie.louie@mongodb.com>2017-10-18 02:21:38 -0400
commit553dff7f3b96b95883b406c7486a04877fbfb094 (patch)
treee6121ed4c3c269d4a0b58671e3ba60d72a7b4952 /jstests/sharding/read_pref.js
parent046a5a01c1bc6eeb05852bed9981cbc457802a00 (diff)
downloadmongo-553dff7f3b96b95883b406c7486a04877fbfb094.tar.gz
SERVER-31579 Tag specific sharding tests as being resource intensive
Diffstat (limited to 'jstests/sharding/read_pref.js')
-rw-r--r--jstests/sharding/read_pref.js4
1 files changed, 4 insertions, 0 deletions
diff --git a/jstests/sharding/read_pref.js b/jstests/sharding/read_pref.js
index 2ca144099f0..0640c347871 100644
--- a/jstests/sharding/read_pref.js
+++ b/jstests/sharding/read_pref.js
@@ -1,6 +1,10 @@
/**
* Integration test for read preference and tagging. The more comprehensive unit test can be found
* in dbtests/replica_set_monitor_test.cpp.
+ *
+ * This test is labeled resource intensive because its total io_write is 706MB compared to a median
+ * of 135MB across all sharding tests in mmapv1.
+ * @tags: [resource_intensive]
*/
// Checking UUID consistency involves talking to a shard node, which in this test is shutdown