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

Refresh rollback id cache on increment

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.4, 3.7.3
    • Affects Version/s: 3.6.2
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-02-12, Repl 2018-02-26

      We currently empty the cache on increment and then refresh it when we call getRollbackID next. This means that server status calls can go to disk when the cache needs to be refreshed. Incrementing the rollback id happens during rollback (which is slow and rare) so it does not matter if we go to storage one more time. We should also refresh the cache on startup for the same reason.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            judah.schvimer@mongodb.com Judah Schvimer
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: