forked from envoyproxy/envoy
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
upstream: fix bug causing hosts to be dropped (envoyproxy#4476)
Previously when a host was moved from an existing priority to a new priority, the update would not cause a host update, causing the host to essentially disappear. This was happening because the code would determine that it knew about the host already (it existed in another priority), but due to a lack of distinction between whether the existing host came from the same priority (should not trigger an update) or another (should trigger another) it would not update the host list when the only new host came from another priority, leaving it empty. The fix involves comparing the list of hosts for the current priority with the list of hosts matched to an existing host. By being in the list of existing hosts, the hosts must either exist in the current priority or another. By comparing these lists we can determine whether the matched host came from a different priority, in which case we mark the host list as changed. Signed-off-by: Snow Pettersen [email protected] Risk Level: Medium, changes host update behavior Testing: Added regression test Docs Changes: n/a Release Notes: n/a Fixes envoyproxy#4473
- Loading branch information
Showing
2 changed files
with
102 additions
and
7 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters