The post-failover wait-primary/expect-job probes used the full masters list led by the just-killed node, triggering libxce bug-854 (positional discovery can't fail over from a dead-first master). Now they use a live-first list excluding the killed primary. NOTE: this exposes a deeper, separate post-failover AVAILABILITY issue (not data loss): the new primary stays stuck in a catch-up loop with a lagging standby (standby[0] lsn=5 < committed_lsn=6) and does not serve clients, so wait-primary still times out. That is a catch-up/serving-readiness liveness concern orthogonal to bug-828's committed-job DATA SAFETY, which is fixed and verified (walcompare committed-prefix identical, jobs preserved on disk). |
||
|---|---|---|
| .. | ||
| autoscaler | ||
| controller | ||
| docs | ||
| frontend | ||
| include | ||
| lib | ||
| nixSupport | ||
| scheduler | ||
| schema | ||
| tools | ||
| worker | ||
| build | ||
| flake.lock | ||
| flake.nix | ||
| meson.build | ||
| meson.options | ||