Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21237

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

    XMLWordPrintableJSON

Details

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

    Description

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

      Attachments

        Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-21129 Allow pipelining of applier work before updating-position/reporting

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-23046 Reimplement operation pipelining applier work before updating-position/reporting

          • Major - P3 - Major loss of function.
          • Closed
          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21298 rollback_index.js fails to wait for replication before continuing

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-21107 Improve protocol version 1 replication throughput

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-21275 Document not found due to WT commit visibility issue

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            People

              matt.dannenberg Matt Dannenberg
              scotthernandez Scott Hernandez (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: