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

Make sure the last applied hash is corresponding to the last applied optime in bgsync start()

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5.4
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Repl 2017-03-06

      Description

      In bgsync start(), the last applied hash is read from the disk outside mutex, but the last applied optime is read while holding the mutex. We need to make sure they are synced.

      The last applied hash is only used for PV0, so this issue will go away when PV0 is deprecated.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              siyuan.zhou Siyuan Zhou
              Reporter:
              siyuan.zhou Siyuan Zhou
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: