summaryrefslogtreecommitdiff
path: root/jstests/sharding/replmonitor_bad_seed.js
diff options
context:
space:
mode:
authorEsha Maharishi <esha.maharishi@mongodb.com>2017-01-24 15:39:37 -0500
committerEsha Maharishi <esha.maharishi@mongodb.com>2017-01-25 10:13:43 -0500
commit8de1704501daa1c99a873554fc0a18632b778f8d (patch)
treee9fe5c38383d329fad2a832795b3bcf21af7b057 /jstests/sharding/replmonitor_bad_seed.js
parent77d3e073ba628f90313590eacbc879e66d629684 (diff)
downloadmongo-8de1704501daa1c99a873554fc0a18632b778f8d.tar.gz
SERVER-27803 add requires_persistence tag to replmonitor_bad_seed.js and authConnectionHook.js
Diffstat (limited to 'jstests/sharding/replmonitor_bad_seed.js')
-rw-r--r--jstests/sharding/replmonitor_bad_seed.js6
1 files changed, 6 insertions, 0 deletions
diff --git a/jstests/sharding/replmonitor_bad_seed.js b/jstests/sharding/replmonitor_bad_seed.js
index efb84783bd4..f6a699a368c 100644
--- a/jstests/sharding/replmonitor_bad_seed.js
+++ b/jstests/sharding/replmonitor_bad_seed.js
@@ -11,6 +11,12 @@
* Another reason for using mongos in this test is so we can use
* connPoolStats to synchronize the test and make sure that the monitor
* was able to refresh before proceeding to check.
+ *
+ * Any tests that restart a shard mongod and send sharding requests to it after restart cannot make
+ * the shard use an in-memory storage engine, since the shardIdentity document will be lost after
+ * restart.
+ *
+ * @tags: [requires_persistence]
*/
(function() {
'use strict';