fc1cc901a1
Publishing the pair only from a satisfied `ack=quorum` wait left both halves at 0 for the entire life of an `ack=leader` workload: the live three-voter cluster served writes at 201/204 and reported `commit_index: 13324714` through `/cluster/status` while `/metrics` showed relay_last_seq 0, relay_durable_seq 0. A gauge nobody can populate is the same blind spot as a gauge that lies. The election driver already ticks every replica ~20x/s and m12p5 seeds the readiness lag gauge from the heartbeat for exactly this reason - the tick flows even when writes do not. Two relaxed stores per tick behind a commit-index lock the quorum waiters already share. |
||
|---|---|---|
| .. | ||
| benches | ||
| config | ||
| src | ||
| tests | ||
| BUILD.bazel | ||
| Cargo.toml | ||