CurOp::reportState reads recovery unit and races with CappedDeleteSideTxn

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2025-02-17
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      CappedDeleteSideTxn swaps out the recovery unit on construction and swaps the original recovery unit back on destruction. This can race with the CurOp thread trying to read storage metrics from the recovery unit. 

      We'll probably need a client lock guard like this when setting the recovery unit in CappedDeleteSideTxn.

            Assignee:
            Shin Yee Tan
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: