queryableBackupMode in sharded clusters fails to apply critical section related entries

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: 5.0.0, 6.0.0, 7.0.0, 8.0.0
    • Component/s: Sharding
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • v8.0, v7.0, v6.0, v5.0
    • CAR Team 2024-02-05, CAR Team 2024-04-29, CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-06-24, CAR Team 2024-07-08, CAR Team 2024-07-22, CAR Team 2024-08-05, CAR Team 2024-08-19, CAR Team 2024-09-02, CAR Team 2024-09-16, CAR Team 2024-09-30, CAR Team 2024-10-14
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      While setting up the queryableBackupMode we can set a time to apply all the oplogs from that time, this is being test today, however, with the work of PM-635 once we're on queryableBackupMode these checks are failing but they shouldn't, because if we're applying an oplog entry related to the critical section, we have to take the collection lock in the observer.

            Assignee:
            Robert Sander
            Reporter:
            Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: