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

Correctly wait for rollback to complete in rollback_with_coalesced_txn_table_updates_during_oplog_application.js

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.0.0-rc1, 5.1.0-rc0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v5.0
    • Sprint:
      Repl 2021-05-31
    • Linked BF Score:
      42

      Description

      When crashAfterRollbackTruncation is false, we didn't wait for rollback to begin, so it's possible that when calling awaitNodesAgreeOnPrimary(), secondary1 has not started rollback, but already saw the new primary, and thus awaitNodesAgreeOnPrimary() will not see the network exception, but after this, rollback starts and connection closed, so the replSetFreeze() command sees the network exception. We should wait for rollback to complete before stepping it up.

        Attachments

          Activity

            People

            Assignee:
            wenbin.zhu Wenbin Zhu
            Reporter:
            wenbin.zhu Wenbin Zhu
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: