pair=site-a mode=active action=kill active=scadabridge-site-a-a victim=scadabridge-site-a-a survivor=scadabridge-site-a-b hit at 2026-11-13T00:49:50Z Active kill: waiting for scadabridge-site-a-b to take over as the active node (victim stays down; budget ~25s + hand-over)... survivor logged the Down at +27s PASS: scadabridge-site-a-b took over as active in 27s with the victim still down (downed the dead oldest, assumed Oldest, re-hosted the singletons). Recovering scadabridge-site-a-a (kill -> start)... Waiting for the victim to rejoin as a ready standby (scadabridge-site-a-a /health/ready)... Recovered: scadabridge-site-a-a is ready as standby (rejoined) 1s after recovery. Checking for a lingering dual-active (10 samples, 1s apart)... Exactly one active node in 10/10 samples. Survivor downing/singleton evidence (last 20 matching log lines from scadabridge-site-a-b): [00:50:16 INF] [Site/scadabridge-site-a-b] Cluster Node [akka.tcp://scadabridge@scadabridge-site-a-b:8082] - Leader is auto-downing unreachable node [akka.tcp://scadabridge@scadabridge-site-a-a:8082] [00:50:16 INF] [Site/scadabridge-site-a-b] Cluster Node [akka.tcp://scadabridge@scadabridge-site-a-b:8082] - Marking unreachable node [akka.tcp://scadabridge@scadabridge-site-a-a:8082] as [Down] [00:50:17 INF] [Site/scadabridge-site-a-b] Member removed [akka.tcp://scadabridge@scadabridge-site-a-a:8082] [00:50:17 INF] [Site/scadabridge-site-a-b] Member removed [akka.tcp://scadabridge@scadabridge-site-a-a:8082] [00:50:17 INF] [Site/scadabridge-site-a-b] ClusterSingletonManager state change [Younger -> Oldest] Akka.Cluster.Tools.Singleton.YoungerData [00:50:17 INF] [Site/scadabridge-site-a-b] ClusterSingletonManager state change [Younger -> Oldest] Akka.Cluster.Tools.Singleton.YoungerData SUMMARY pair=site-a mode=active action=kill down_logged_s=27 rejoin_s=1 Drill complete. Verify on the Health dashboard / Overview that both nodes show Up and exactly one is Primary.