step_down_lock is not needed when writes are mirrored during async stepdown

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Layered Tables
    • None
    • Storage Engines - Foundations
    • 167.078
    • Storage Execution 2026-09-14, Storage Execution 2026-09-28
    • None

      WT-18419 enables mirrored writes to both stable and ingest during async stepdown, making the synchronization through step_down_lock obsolete because it's only needed for detecting multi-table write conflicts. However, because we still support ingest-only writes, we still need to conditionally acquire the lock. We will be able to remove the lock entirely when we drop the ingest-only mode.

            Assignee:
            Wei Hu
            Reporter:
            Wei Hu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: