Investigation: understand why the acquisition of the critical section doesn't have waitForLock:true

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Catalog and Routing
    • Fully Compatible
    • Sharding EMEA 2023-04-17, Sharding EMEA 2023-05-01, Sharding EMEA 2023-07-24, Sharding EMEA 2023-09-04, Sharding EMEA 2023-09-18, Sharding EMEA 2023-10-02, Sharding EMEA 2023-10-16, Sharding EMEA 2023-10-30, CAR Team 2023-11-13, CAR Team 2023-11-27, CAR Team 2023-12-11, CAR Team 2023-12-25, CAR Team 2024-01-08, CAR Team 2024-01-22, CAR Team 2024-02-05, CAR Team 2024-02-19, CAR Team 2024-03-04, CAR Team 2025-04-14, CAR Team 2025-04-28, CAR Team 2025-05-12, CAR Team 2025-05-26, CAR Team 2025-06-09, CAR Team 2025-06-23, CAR Team 2025-07-07, CAR Team 2025-07-21, CAR Team 2025-08-04
    • 1
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The goal of this task is to understand why the command that acquires the recoverable critical section doesn't have the waitForLock:true.

      This investigation is related to this PR comment.

              Assignee:
              Jordi Serra Torrens
              Reporter:
              Sergi Mateo Bellido
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: