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()

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.5.4
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2017-03-06

      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.

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

              Created:
              Updated:
              Resolved: