From 54d53df956a8e06a45f3f0018bbc9f787590c516 Mon Sep 17 00:00:00 2001 From: Rongsong Shen Date: Tue, 11 Aug 2026 07:58:50 +0000 Subject: [PATCH] docs(component-failover-adoption): mark task 3.1 complete MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Scheduler's unified connect pipeline is implemented, tested (RED→GREEN verified), and live-validated against a 3-node HA controller cluster (standby-first candidate list joins correctly via xcecli failover). See a9f283d. Co-Authored-By: Claude Sonnet 5 Claude-Session: https://claude.ai/code/session_01FYSEeLmzjtD4RLDuUDhLoK --- .kiro/specs/component-failover-adoption/tasks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.kiro/specs/component-failover-adoption/tasks.md b/.kiro/specs/component-failover-adoption/tasks.md index 275ac279..417d3a18 100644 --- a/.kiro/specs/component-failover-adoption/tasks.md +++ b/.kiro/specs/component-failover-adoption/tasks.md @@ -51,7 +51,7 @@ - _Depends: 2.1, 2.2_ - [ ] 3. Scheduler: unified candidate-list connect, decision-publish redelivery, and runtime reconnect -- [ ] 3.1 (P) Replace scheduler's dual connect mechanisms with the single unified pipeline +- [x] 3.1 (P) Replace scheduler's dual connect mechanisms with the single unified pipeline - Delete the scheduler's inline per-candidate loop and its separate single-host branch used when no candidate list is configured — both bypass the shared candidate-list validation and conversion helper entirely today - Build exactly one validated candidate list before connecting, whether from an operator-supplied peer list or synthesized as a single candidate from the existing default when none was given, then run it through the shared helper and connect once - Register a rejoin callback that only sets a flag and returns immediately, for the same self-deadlock reason as worker's