diff options
| author | Geert Bosch <geert@mongodb.com> | 2018-06-12 17:27:01 -0400 |
|---|---|---|
| committer | Geert Bosch <geert@mongodb.com> | 2018-06-25 16:47:18 -0400 |
| commit | ab0c426e60c4bdcc49b5a48a93f84828414d5ba6 (patch) | |
| tree | 59eea717b0cae54e39b4981d654fd58d31d7b286 /jstests/sharding/move_chunk_wc.js | |
| parent | 5339c9a55181662545652ab7106c8f4e55109327 (diff) | |
| download | mongo-ab0c426e60c4bdcc49b5a48a93f84828414d5ba6.tar.gz | |
SERVER-35591 Remove MMAPv1 testing
Diffstat (limited to 'jstests/sharding/move_chunk_wc.js')
| -rw-r--r-- | jstests/sharding/move_chunk_wc.js | 4 |
1 files changed, 0 insertions, 4 deletions
diff --git a/jstests/sharding/move_chunk_wc.js b/jstests/sharding/move_chunk_wc.js index 3d7e1e9edb9..601b327b76e 100644 --- a/jstests/sharding/move_chunk_wc.js +++ b/jstests/sharding/move_chunk_wc.js @@ -6,10 +6,6 @@ * 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'); |