Background

Design: WRITING-39975. Scope: WRITING-39974. Epic: SPM-4886. Related: WT-18419.

During an elegant step-down a node writes to both the ingest and the stable table. A remove in that window must behave the same way with blind_remove set.

Change

• A blind remove on a mirrored write gives the same result as without the option for existing keys, and returns success for missing keys.
• Both tables end up correct, with no lone or consecutive tombstones.

Tests

Python tests in the same PR cover:

• A blind remove during the mirrored window for keys that exist, are missing, and are already deleted.
• Both tables hold the expected state afterwards.
• Stacked deletes in the window, with reads at timestamps in between.

Acceptance criteria

• Behaviour matches the design. New tests pass, and fail without the change.

Depends on

Leader blind remove ticket.