* Changes resmoke.py to propagate --storageEngineCacheSizeGB as
--inMemorySizeGB when running with the InMemory storage engine.
* Changes the mongo shell to propagate
TestData.storageEngineCacheSizeGB as --inMemorySizeGB when running
with the InMemory storage engine.
* Sets --storageEngineCacheSizeGB=4 when running with the InMemory
storage engine in Evergreen.
This patch creates separate 'logComponentVerbosity' default settings
for tests running running locally versus those running in
Evergreen. This only applies to tests run using resmoke.py. We detect
that a test is running in Evergreen by checking if resmoke received
an EVERGREEN_TASK_ID parameter.
This patch changes the format of the TestData.setParameters variable we
pass to the mongo shell from within resmoke. We now pass this value as a
JavaScript object, where keys are parameter names and values are the
values to set for that parameter. Additionally, we also consolidate the
hard-coded 'logComponentVerbosity' default settings into resmoke, instead of
having them mixed between servers.js and resmoke's programs.py. Now, any
mongod processes started either directly by resmoke or via a mongo shell
that was started by resmoke will receive default log verbosity settings
from a value defined in resmoke.
When deleting the donor range after migrating a chunk off of a shard,
the range deleter will schedule the deletion at some time in the future,
according to a server parameter orphanCleanupDelaySecs, which defaults
to 900, or 15 minutes. It does not delay range deletions preparatory to
migrating a range in, and does not put off deleting the donor range if
the moveChunk command has set the option _waitForDelete.
The file jstests/sharding/write_commands_sharding_state.js had CR (0x0D)
line endings, which made the patch fail lint. The substantive changes
in the file were to add "_waitForDelete" options to the moveChunk
commands.
Forwards the value for resmoke.py's --numClientsPerFixture command line
option to the mongo shell running the test. This enables the fuzzer to
know if there are concurrent clients running the test.
Adds a new core_small_oplog_rs_kill_secondaries.yml suite that after
running tests for a certain period of time (defaults to 30 seconds),
resmoke.py will send a SIGKILL to all of the replica set's secondaries.
Each node is then restarted individually with the primary disabled to
verify it reaches the SECONDARY state within 5 minutes of starting up.
