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

Use awaitMajorityCommitted in standalone_replication_recovery_idempotent.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.3, 4.3.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Repl 2020-01-13
    • Linked BF Score:
      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

            Assignee:
            lingzhi.deng Lingzhi Deng
            Reporter:
            lingzhi.deng Lingzhi Deng
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: