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

CurOp::reportState reads recovery unit and races with CappedDeleteSideTxn

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • Execution Team 2025-01-06, Execution Team 2025-01-20
    • 0

      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:
            shinyee.tan@mongodb.com Shin Yee Tan
            Reporter:
            shinyee.tan@mongodb.com Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: