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

Use getLastAppliedOpTime rather than getHeartbeatAppliedOpTime for checking primary's position

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.2.4, 4.3.4, 4.0.17
    • Replication
    • None
    • Fully Compatible
    • v4.2, v4.0
    • Repl 2020-02-24

    Description

      The OpTime used to check the primary's OpTime is ahead of mine in SERVER-34768 isn't consistent between the check and the log.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34768 Rollback can fail if run against a lagged node that catches up

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

          Activity

            People

              siyuan.zhou@mongodb.com Siyuan Zhou
              siyuan.zhou@mongodb.com Siyuan Zhou
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: