Cache the oplogTruncateAfterPoint in memory and only update it when it changes

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0, 4.4.5
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • v4.4
    • Execution Team 2020-12-28, Execution Team 2021-02-08
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently the oplogTruncateAfterPoint is getting redundantly written to even when the value is not changing – imagine a quiet system, still periodically running the code to flush data to disk (nothing to flush, of course), before which we always do an oplogTruncateAfterPoint update regardless of anything.

            Assignee:
            Dianna Hohensee (Inactive)
            Reporter:
            Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: