linkerd2/proxy
Brian Smith f931dec3b3
Proxy: Completely replace current set of destinations on reconnect (#632)
Previosuly, when the proxy was disconnected from the Destination
service and then reconnects, the proxy would not forget old, outdated
entries in its cache of endpoints. If those endpoints had been removed
while the proxy was disconnected then the proxy would never become
aware of that.

Instead, on the first message after a reconnection, replace the entire
set of cached entries with the new set, which may be empty.

Prior to this change, the new test
outbound_destinations_reset_on_reconnect_followed_by_no_endpoints_exists
passed already
but outbound_destinations_reset_on_reconnect_followed_by_add_none
and outbound_destinations_reset_on_reconnect_followed_by_remove_none
failed. Now all these tests pass.

Fixes #573

Signed-off-by: Brian Smith <brian@briansmith.org>
2018-03-29 16:50:08 -10:00
..
controller-grpc Turn off the `use_logging` default feature of quickcheck. (#465) 2018-02-26 16:04:58 -10:00
convert Prepare for the v0.3.0 release (#406) 2018-02-21 11:14:11 -08:00
futures-mpsc-lossy Prepare for the v0.3.0 release (#406) 2018-02-21 11:14:11 -08:00
router Proxy: Upgrade h2 and indexmap crates (#572) 2018-03-14 12:35:38 -07:00
src Proxy: Completely replace current set of destinations on reconnect (#632) 2018-03-29 16:50:08 -10:00
tests Proxy: Completely replace current set of destinations on reconnect (#632) 2018-03-29 16:50:08 -10:00
Cargo.toml proxy: add SIGTERM and SIGINT handlers (#581) 2018-03-16 18:53:20 -07:00
Dockerfile Actually skip flaky tests on CI and in Docker (#626) 2018-03-26 17:11:06 -07:00