This test fails sporadically due to causes unrelated to the feature this
test was originally intended to test. Removing this test for now.
For C++ unit test coverage, refer to mongo/db/storage/flow_control_test.cpp.
This eliminates the need for the FAILURE status codes in
PlanStage and PlanExecutor, and brings query execution's
error reporting more in line with that of the rest of the
server. It also makes it easier for future implementations
of PlanExecutor to comply with the interface.
* 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.
The `srv-uri` test needs to explicitly decline to use SSL, since
the new `mongo+srv://` URI scheme implicitly turns on SSL. On
SSL based configurations, the test will fail to connect to
localhost when SSL is enabled.
The shell now supports parsing and handling `mongo+srv://` style URIs,
as part of the DNS Seedlist support. These URIs require DNS SRV and
TXT record lookups, for extra configuration options. The shell also
supports a (limited) form of connection-failover -- when initially
connecting to a non-replica-set cluster, the shell will try each
host listed, in order, until a connection can be established.
Also removed jstests/libs/election_timing_test.js
Since disabling the timing checks in SERVER-26142, election_timing.js is
reduced to a series of test cases that trigger elections by stepping
down or stopping the primary under various election configurations
(protocol version 0 or 1).
A typical election_timing.js test run typically takes longer than 10
minutes which is a little excessive compared to existing replica set tests.
This makes election_timing.js redundant with existing C++ unit tests and JS
tests in jstests/replsets.
