-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dns: de-dup returned entries #433
Comments
To what extent does order and multiplicity matter? Could we just pass a set to ResolveCb instead of a list in DnsResolver? Might the upper level cluster code use multiplicity to influence weight or order to determine preference? |
Order doesn't currently matter, but the code in: Does not correctly handle duplicates. IMO, it would be better to fix the above code since that will cover not only DNS, but SDS, etc. also, and dealing with duplicates is really an envoy "problem" and not a DNS problem. |
Previously we would incorrectly keep adding hosts and essentially leak memory. fixes #433
Previously we would incorrectly keep adding hosts and essentially leak memory. fixes #433
Automatic merge from submit-queue. [DO NOT MERGE] Auto PR to update dependencies of mixerclient This PR will be merged automatically once checks are successful. ```release-note none ```
…roxy#433) Those tests occasionally timeout on istio/envoy CI. Signed-off-by: Piotr Sikora <piotrsikora@google.com>
envoyproxy#433) * zh-translation: docs/root/configuration/listeners/network_filters/thrift_proxy_filter.rst * fix translate
Adds support for setting the domain used in the base cluster of the Envoy config. This is necessary until `dynamic_forward_proxy` is working (see #433). Android change will come in a follow-up PR. Risk Level: Low Testing: Locally on demos & unit tests Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
Adds support for setting the domain used in the base cluster of the Envoy config. This is necessary until `dynamic_forward_proxy` is working (see #433). Android change will come in a follow-up PR. Risk Level: Low Testing: Locally on demos & unit tests Signed-off-by: Michael Rebello <me@michaelrebello.com> Signed-off-by: JP Simard <jp@jpsim.com>
This was raised here: #431
If DNS returns the same entry multiple times, we will keep adding a host and effectively leak. Either the DNS impl itself should dedup, or the dymamic cluster add/remove code should do it.
cc @htuch
The text was updated successfully, but these errors were encountered: