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

Remove _oplogMaxAtStartup in WiredTigerOplogManager

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.1.6
    • None
    • Storage
    • None
    • Fully Compatible
    • Storage NYC 2018-11-19

    Description

      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.

      Attachments

        Activity

          People

            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            xiangyu.yao@mongodb.com Xiangyu Yao (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: