[v8.0] Inconsistent state between opCtx and recovery unit after aborting WUOW

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.0.12
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Server Integration
    • ALL
    • SESI - 2025-09-16
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When user writes are disabled, aborting a wuow does not update the state of the opCtx, leaving its internal _ruState inconsistent with the state of the recovery unit. It also doesn't take into account nesting of wuow's. All of this can lead to incorrect construction of subsequent wuow's, as it happened in this patch.

      I haven't checked whether this bug is in master, but it has been fixed after SERVER-93994.

              Assignee:
              Clarisse Cheah
              Reporter:
              Aitor Esteve Alvarado
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: