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

Do not read at lastApplied while already holding the PBWM lock on secondaries

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.11, 4.2.0-rc2, 4.3.1
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0
    • Sprint:
      Execution Team 2019-06-17
    • Case:
    • Linked BF Score:
      47

      Description

      When secondary reads must take the PBWM lock to read without a timestamp, all writes become visible. At this point, an operation holding the PBWM lock should not be allowed to start reading with a timestamp in a different snapshot, because writes and catalog operations may appear to vanish.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: