docs(archreview): live finding — keep-oldest downs the survivor on oldest-crash (#459) #462

Merged
dohertj2 merged 1 commits from docs/459-oldest-crash-live-finding into master 2026-07-15 10:03:51 -04:00
Owner

Live 2-container verification for #459. Hard-killing the oldest node makes the younger survivor down itself (SBR DownReachable including myself) -> no failover. Reproduced twice. Confirms #459 is real and disproves Option A. See archreview/plans/artifacts/459-oldest-crash-live-finding-2026-07-15.md. Refs #459.

Live 2-container verification for #459. Hard-killing the oldest node makes the younger survivor down itself (SBR DownReachable including myself) -> no failover. Reproduced twice. Confirms #459 is real and disproves Option A. See archreview/plans/artifacts/459-oldest-crash-live-finding-2026-07-15.md. Refs #459.
dohertj2 added 1 commit 2026-07-15 10:03:48 -04:00
docs(archreview): live finding — keep-oldest downs the survivor on oldest-crash (#459)
v2-ci / build (pull_request) Successful in 4m27s
v2-ci / unit-tests (pull_request) Failing after 11m36s
d7470c7960
2-container docker-dev rig: hard-killing the oldest node makes the younger
survivor down ITSELF (SBR DownReachable including myself -> CoordinatedShutdown)
-> no failover, total outage. Reproduced twice. Confirms #459 is REAL and
disproves Option A (keep keep-oldest). Baseline ServiceLevel 250(leader)/240(follower)
captured before the kill. Documents why (textbook 2-node keep-oldest limitation;
down-if-alone doesn't rescue a crashed oldest) and why the in-process
HardKillFailoverTests gave false confidence (Transport.Shutdown keeps the
ActorSystem alive, not a real crash). Fix needs Option B (witness+keep-majority)
or Option C (DB-lease arbiter).
dohertj2 merged commit b980eeb148 into master 2026-07-15 10:03:51 -04:00
Sign in to join this conversation.