A proxy dispatches requests over a constrained number of routes. When the router's upper bound is reached---and potentially in other future scenarios---router capacity is created by removing unused routes, their load balancers, and all related endpoint stacks. However, in the current regime, the controller subsystem will continue to monitor discovery observations. As the number of active observations expands over time, the controller task ends up with more and more work to do. This change introduces a shared atomic boolean between the resolution returned to the load balancer and the state maintained when communicating with the service. Before the controller polls its active resolutions, it first ensures that all unused resolutions are dropped. |
||
---|---|---|
.github | ||
proxy | ||
CONTRIBUTING.md | ||
Cargo.lock | ||
Cargo.toml | ||
DCO | ||
LICENSE |