Operations FAQ

Does a config reload drop active connections? No. Dryad Gateway keeps existing connections bound to the routing table that was active when they were accepted. Only new connections use the reloaded config.

What happens if all backends for a route are unhealthy? The route returns 503 Service Unavailable and the failure is recorded in the access log with backend: none-available. The route is retried on every health-check interval until a backend recovers — see GET /routes/{routeId}/health to inspect that history directly.

Can rate limits be shared across routes? Not directly. Each route has its own token bucket. To approximate a shared limit across routes, point them at the same admin_tokens scope and enforce a combined limit client-side, or front them with a single route that fans out internally. Runtime limit changes go through POST /ratelimits/{routeId}.

Is there a hot-reload for TLS certificates? Yes. Placing a new certificate and key at the configured paths and sending SIGHUP rotates the TLS certificate along with the rest of the config, with no connection drops, for the same reason config reloads are safe.