SERVER-14728 Shard depends on string comparison of replica set connection string
SERVER-14448 Fix Date handling in replSetGetStatus
SERVER-14442 Fix handling of "self" when preparing replSetUpdatePosition commands
Revert "SERVER-14728 Shard depends on string comparison of replica set connection string"

This reverts commit b3787777795434829a3b512c06b5a0a508d81467.
SERVER-14825 Add utility methods to C++ unit tests for capturing and examining log messages.
SERVER-14788 Get isSelf functionality from ReplCoordinatorExternalState in parseReplSetSeedList.

This makes parseReplSetSeedList usable in ReplicationCoordinatorImpl.
SERVER-14788 Simplify the fixture for running tests in repl_coordinator_impl_test.

These simplifications remove some memory leaks and make it easier to follow the initialization
logic.  This is prerequisite to changes testing the loading local configurations during
startReplication().
SERVER-14506 special top chunk logic can move max chunk to a shard with incompatible tag

Make DistributionStatus store ChunkTypes instead of BSONObj
SERVER-14506 special top chunk logic can move max chunk to a shard with incompatible tag
SERVER-5092 qualify LogstreamBuilder and getThreadName in MONGO_LOG macros
SERVER-14467 log S2 debug messages as query log message at level 5
SERVER-11107 Server SSL certificate expiration date check tests

Closes #734

Signed-off-by: Benety Goh <benety@mongodb.com>
Revert "Revert "SERVER-14728 Shard depends on string comparison of replica set connection string""

This reverts commit d261864e9156af7ecc3d0491111dffa0161e9d0d.
SERVER-14728 Shard depends on string comparison of replica set connection string

Fix iterator incompatible issue.
SERVER-14817 fixed benchRun so that it does not call auth() on every operation.

Closes #733

Signed-off-by: Benety Goh <benety@mongodb.com>
SERVER-14135 Improve clarity around locking rules in the header for ReplicationCoordinatorImpl
SERVER-14838: Fix shutdown failures

1. On Solaris, we race between the main thread, and signal thread. The
main thread wins, and returns EXIT_NET_ERROR. Previously, we use to work around
this by just sleeping on the main thread.

2. If we exit early due to missing db path, OperationContext asserts
because the storage engine has not been started yet.
move some jstests to use bulk insert to make tests faster
SERVER-14800 Replace some masserts with invariant calls in locking
SERVER-14788 Do not start threads in ReplicationExecutor's constructor.

By not starting threads in the ReplicationExecutor constructor, we can safely construct
it when constructing the ReplicationCoordinatorImpl that owns it, which allows us to
get rid of the weird behavior where we pass a NetworkInterface* to startReplication(),
and further allows us to clean up the concurrency rules for startReplication().