ReplSetTest.prototype.awaitReplication reads directly from the oplog collection causing false positives

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Repl C (11/20/15)
    • 0
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            Matt Dannenberg (Inactive)
            Reporter:
            Scott Hernandez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: