prisma-risk / tsoracle / 34882714147

97%

Build Type

push

github

Committed by web-flow

Commit Message

feat(driver-openraft): persist stamping leases behind write version 7 (#708)

The openraft driver inherited `LeasesUnsupported`, so no replicated tsoracle cluster could grant a stamping lease. This adds lease persistence as a format feature.

A new `SetLeases` log command replaces the durable lease set wholesale and carries the raft term the server's leader epoch named when it projected the set. Apply installs the set only when the entry's own log id carries that term. The apply-time max that fences a stale high-water advance cannot fence a full-set replacement, so a set projected before a leadership change would otherwise overwrite leases granted after it. A fenced apply surfaces as `ConsensusError::Fenced`.

Lease records use a frozen driver-local layout that re-validates holder length and strict lease-id ordering on every decode. The v7 snapshot carries the lease set; a frozen v5 layout keeps v5 and v6 snapshots byte-identical, and encoding leases below v7 fails loud. `LEASE_WRITE_VERSION` is 7 and `MAX_READABLE_VERSION` rises to 7. Until the cluster activates it, `persist_leases` returns the new `ConsensusError::LeasesNotActivated`, which the server maps to a bare FAILED_PRECONDITION, and `load_leases` returns an empty set. The host trait gains `current_leases` and `submit_set_leases` with `LeasesUnsupported` defaults, so existing hosts keep compiling.

Signed-off-by: Sebastian Thiebaud <sebastian@prismarisk.com>

Coverage Stats

574 of 581 new or added lines in 10 files covered. (98.8%)

2 existing lines in 1 file now uncovered.

18970 of 19651 relevant lines covered (96.53%)

315862.13 hits per line