Once the OpTime is updated then progress can be reported and used upstream, or locally for replication.
Cannot read own write after drop with read/write concern "majority" with inMemory storage engine
Remove read_concern_majority_passthrough_WT on Enterprise RHEL 6.2 (inMemory) on 3.2 branch
implement "j" flag in write concern apply to secondary as well as primary
Make periodic write flushing a service of the storage system
Enable ReadConcern.Majority tests without journaling