Refuses to activate a dshackle config routing >1 upstream for the same chain (any kind/client) — we cannot attribute traffic to multiple nodes behind one proxy (no per-upstream request-count metric; conn-seconds biases it), and the attribution model + placement planner both assume 1:1. Wire into reload_dshackle.sh BEFORE the reload so a drifting config can never go live. Host-local by design (the repo doesn't track host->dshackle assignment; 1:1 is only checkable against the assembled dshackle config at /root/rpc/main_configs). See /root/proxy-1to1-invariant-plan.md. Co-Authored-By: Claude <noreply@anthropic.com>
4.3 KiB
4.3 KiB