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

Have internal oplog helpers be resilient to EBUSY on opening cursors

    • 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
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-06-01
    • 37

      Opening a WT cursor can fail with an EBUSY if a verify or salvage is being run on the table. This gets turned into a WriteConflictException. Internal oplog helpers (e.g: getLatestOplogTimestamp) should retry in these cases. To avoid unnecessary spinning in tests, our foreground validate hooks should omit validating the oplog. The background validation hooks are safe to continue running on the oplog.

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

              Created:
              Updated:
              Resolved: