Expand description
Per-write acknowledgement policy and progress receipts. Acknowledgement thresholds do not establish a global mutation order.
The receiving node freezes replica eligibility, region labels, and the
effective count before apply. A processing acknowledgement means that the
replica processed this mutation and retains its equal-or-newer LWW winner;
it does not promise that the submitted value remains the winner. The local
acknowledgement follows ordinary apply completion, which may only enqueue
persistence and return before a store flush. Remote acknowledgements
satisfy the stronger of the sender’s configured fence and the per-write
minimum. minimum_durability explicitly requests a store or stable fence.
Evidence records the actual reached fence for each counted identity, the
submitted operation/version floor and the exact frozen eligible set. Local
default evidence certifies memory apply even if a background flush races it.
Structs§
- Write
Acknowledgement - Write
Concern Evidence - Exact frozen eligible identities and reached fences for one submitted floor. The deterministic digest identifies the set, not a placement epoch or lease.
- Write
Concern Options - Per-write wait policy. Timeout starts when the receiving node applies the update. Transport and actor admission have their own deadlines.
- Write
Concern Options Builder - Use builder syntax to set the inputs and finish with
build(). - Write
Concern Receipt - Actual processing acknowledgement progress. The receiving node always
counts as one after ordinary apply completion. Certified evidence reports
actual local and remote fences; a timed-out or failed-fence receipt may retain
local progress below the requested durability. No failed write is rolled back.
An unknown replica count is represented by
Nonefor local-only writes. - Write
Operation Evidence - Submitted operation identity. ACKs certify an equal or newer LWW winner, not immutable payload/log presence or a distributed atomic snapshot.
Enums§
- Write
Concern - Total acknowledgements, including the receiving node.
- Write
Concern Outcome - Write
Concern Policy Error - Write
Durability - Actual minimum fence reached. Buffered store commit does not imply fsync.