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

Use getLastAppliedOpTime rather than getHeartbeatAppliedOpTime for checking primary's position

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.2.4, 4.3.4, 4.0.17
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • v4.2, v4.0
    • Repl 2020-02-24

      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.

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

              Created:
              Updated:
              Resolved: