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

Secondary reads before the last-applied timestamp is set should take the PBWM lock and read at a timestamp

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • 3.7.9
    • Storage
    • None
    • Storage Execution
    • ALL

    Description

      When a local snapshot is not available because the last-applied timestamp is not yet set, we default to reading without a timestamp, and without the PBWM lock.

      Note that this is not necessarily a problem at the moment. If no last-applied timestamp is set, there are no replicated collections to read from, so a read wouldn't even be possible in this period.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: