Resharding aggregation query should not acquire RSTL-IX when waiting lastStableRecoveryTimestamp

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.1, 7.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v7.2
    • Repl 2024-01-22
    • 136
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-81381, we added logic in waitForReadConcern for the resharding aggregation query to wait lastStableRecoveryTimestamp to pass the snapshot read timestamp. We also do checkpoint in the waitForReadConcern code and it requires Global-IS lock. By default, acquiring Global-IS lock also acquires RSTL-IX. Because checkpointing is not interruptible through opCtx, a slow checkpoint can block stepup/stepdown, especially in slow environments like Windows Debug.

              Assignee:
              Jiawei Yang
              Reporter:
              Jiawei Yang
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: