-
Type: Bug
-
Resolution: Done
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Replication, Testing Infrastructure
-
None
-
Fully Compatible
-
ALL
-
Repl C (11/20/15)
-
0
Because of changes in the way oplog entries are processed, the latest written oplog entries may be ahead of what has been journaled, or snapshotted, and reported and should not be used for "waiting for replication".
ReplSetTest.prototype.awaitReplication must be re-written to use replSetGetStatus/serverStatus(oplog:true) from each node instead of querying the oplog directly.
In addition the function should allow waiting for more types of replication, like for readConcern.majority, or readAfterOptime (which could be used to test for the former).
- depends on
-
SERVER-21129 Allow pipelining of applier work before updating-position/reporting
- Closed
-
SERVER-23046 Reimplement operation pipelining applier work before updating-position/reporting
- Closed
- is depended on by
-
SERVER-21298 rollback_index.js fails to wait for replication before continuing
- Closed
- is related to
-
SERVER-21107 Improve protocol version 1 replication throughput
- Closed
- related to
-
SERVER-21275 Document not found due to WT commit visibility issue
- Closed