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

Background validation uses the kNoOverlap read source instead of kAllDurableSnapshot to prevent us from having to take the PBWM lock on secondaries

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.8.0, 4.4.2
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-05-04, Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-24, Execution Team 2020-10-05
    • Linked BF Score:
      37

      Description

      If the PBWM lock is held during the entire background collection validation, then on secondaries it could stall replication, which is undesirable. After opening all of the collection and index cursors, we can release the PBWM lock.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              milkie Eric Milkie
              Reporter:
              gregory.wlodarek Gregory Wlodarek
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: