Remove _oplogMaxAtStartup in WiredTigerOplogManager

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.6
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-11-19
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We no longer need _oplogMaxAtStartup as the lower bound for visibility timestamp because we explicitly set oplogReadTimestamp to be the same value as _oplogMaxAtStartup on startup and it will only grow beyond that value.

      Code and comments related to this variable can be removed.

            Assignee:
            Xiangyu Yao (Inactive)
            Reporter:
            Xiangyu Yao (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: