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

fix oplog cursor leak in getEarliest/LatestOplogTimestamp()

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.4.0-rc7, 4.7.0
    • Affects Version/s: None
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-05-18

      WiredTigerRecordStore::getLatestOplogTimestamp() and WiredTigerRecordStore::getEarliestOplogTimestamp() open a new cursor every time they are called. This should be switched to using the cached cursor functionality provided in WiredTigerCursor.

        1. Screen Shot 2020-05-14 at 9.24.21 PM.png
          Screen Shot 2020-05-14 at 9.24.21 PM.png
          116 kB

            Assignee:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Reporter:
            milkie@mongodb.com Eric Milkie
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: