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

Fast-path caching of oldest oplog entry

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.4
    • Replication, WiredTiger
    • None
    • Fully Compatible
    • Execution Team 2020-01-13, Execution Team 2020-01-27, Execution Team 2020-02-10, Execution Team 2020-02-24

    Description

      When the serverStatus command is invoked, its oplog section collects the most recent applied optime and retrieves the first entry from the oplog collection. Because the oldest op is less likely to be present in the WT cache, this may require us to read from disk, and possibly to wait for space during periods of high cache pressure.

      Given the frequency with which serverStatus is called for FTDC collection and by the Monitoring Agent, we should consider implementing a separate caching mechanism and fast-path this query to avoid I/O and WT cache contention.

      Attachments

        Issue Links

          Activity

            People

              milkie@mongodb.com Eric Milkie
              bernard.gorman@mongodb.com Bernard Gorman
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: