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

Use awaitMajorityCommitted in standalone_replication_recovery_idempotent.js

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.2.3, 4.3.3
    • Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2020-01-13
    • 12

    Description

      awaitReplication only waits for the lastAppliedOpTime. After calling awaitReplication, the commit point could still be behind. For prepared transactions testing, we have awaitMajorityCommitted which waits for the commit point as known by the primary.

      We should change standalone_replication_recovery_idempotent.js to use awaitMajorityCommitted.

      And it seems that it is a common mistake to use awaitReplication in prepared transactions testings, maybe we could also move the logic in awaitMajorityCommitted to awaitReplication to have it also wait for the commit point.

      Attachments

        Activity

          People

            lingzhi.deng@mongodb.com Lingzhi Deng
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: