reload_dshackle: cut gateway connections on handler completion (~30 ms) instead of a fixed 3 s settle #81

Merged

claude merged 1 commits from reload-settle-poll into main

2026-09-19 09:54:22 +00:00

Author	SHA1	Message	Date
rob	6f4b297733	reload_dshackle: cut gateway connections as soon as the SIGHUP handler reports completion (~30ms) instead of after a fixed 3s settle The reload is in-process and takes 10-30 ms; the fixed sleep was the window in which a removed upstream was already unrouted in dshackle while the gateway still held the old announcements and kept sending queries it could no longer answer. Poll the log for 'Reloading config has been completed' (or the fail/drop markers), SETTLE stays the upper bound. Operator 2026-09-19. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KjqejYycVyVvrxV9aTDhgX	2026-09-19 09:50:03 +00:00

Author

SHA1

Message

Date

rob

6f4b297733

reload_dshackle: cut gateway connections as soon as the SIGHUP handler reports completion (~30ms) instead of after a fixed 3s settle

The reload is in-process and takes 10-30 ms; the fixed sleep was the window in
which a removed upstream was already unrouted in dshackle while the gateway still
held the old announcements and kept sending queries it could no longer answer.
Poll the log for 'Reloading config has been completed' (or the fail/drop
markers), SETTLE stays the upper bound. Operator 2026-09-19.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KjqejYycVyVvrxV9aTDhgX

2026-09-19 09:50:03 +00:00

reload_dshackle: cut gateway connections on handler completion (~30 ms) instead of a fixed 3 s settle #81

1 Commits