Loading...

XML

Word

Printable

JSON

Choose blind_remove when getting a cursor, only for removes that oplog application applies on a follower, and only when the kill switch allows it. Never for reads or on a leader. Do not use WT_CURSOR::reconfigure.
Before each WT_CURSOR::remove, assert in debug builds if the node is the leader and the cursor has blind_remove set.

Only follower oplog application removes use the option. The assert fires in a debug-build test that forces the leader case.

Kill-switch ticket, WT-18920, WT-18921.

depends on

SERVER-137753 Add a kill-switch server parameter for WiredTiger blind remove

WT-18920 Implement follower blind remove in the layered cursor

WT-18921 Step-up ingest drain tolerates orphan removes from blind remove

is depended on by

SERVER-137755 Remove the testing proctor override and run tests with blind remove enabled