Until SERVER-30679 is implemented, setting causallyConsistentReads=true in the mongo shell's SessionOptions object won't cause "afterClusterTime" to be injected into the readConcern of the command request. In order to test the fuzzer with causal consistency enabled without waiting for those changes, we should call Mongo.prototype.setCausalConsistency() directly on the connection object via load("jstests/libs/override_methods/enable_causal_consistency.js").

A new resmoke.py YAML suite and Evergreen tasks should be defined to run the fuzzer with causal consistency enabled. The YAML suite should be adapted from the existing jstestfuzz_sharded.yml and causally_consistent_jscore_passthrough.yml suites where it'll run tests from the jstestfuzz/out/ directory against a sharded cluster with two replica set shards. Additionally, the new suite should define a TestData.runningWithCausalConsistency=true option so that the fuzzer can implement configuration-specific blacklisting similar to what is done with TestData.ignoreCommandsIncompatibleWithInitialSync=true in the jstestfuzz_replication_initsync.yml test suite.

Names of new resmoke.py YAML suites

• jstestfuzz_sharded_causal_consistency.yml

Names of new Evergreen tasks

• jstestfuzz_sharded_causal_consistency
• jstestfuzz_sharded_causal_consistency_WT
• jstestfuzz_concurrent_sharded_causal_consistency
• jstestfuzz_concurrent_sharded_causal_consistency_WT

The new Evergreen tasks should be run on the following build variants:

• Enterprise RHEL 6.2
• Enterprise RHEL 6.2 (inMemory)
• SSL Windows 2008R2
• SSL OS X 10.10
• ASAN SSL Ubuntu 16.04