Anubhav
Anubhav
> wait_for_warm_on_init @zuercher - this is set to true by default.
@lambdai / @howardjohn - will be glad if you can throw some light on this one. Similar to https://github.com/envoyproxy/envoy/issues/20562
Appears that envoy is marking itself ready even when DNS resolution failed with the following error codes as per C-Ares: Error codes: 1. 12 - ARES_ETIMEOUT 2. 11 - ARES_ECONNREFUSED...
After updating Envoy's code with increased DNS resolution timeout, and increased no. of retries, we encountered a reduction of errors by 90%. The experiment proved that the issue is rooted...
When there are 2 STRICT DNS clusters with the same endpoint, envoy does 2 DNS resolutions. Can the DNS resolution mechanism be optimized to avoid duplicate DNS resolutions? cc: @alyssawilk...
Hi @jithine, is this part of the roadmap yet? Will be very useful
@ramaraochavali - would appreciate your input. Thanks!
Thanks for the input @ramaraochavali. I am not aware of the internals of the RLQ, but it appears to be async. But there are some limitations on the RLQ: 1....
@yanavlasov - does envoy honor the quota API, is the change required on the reference implementation of the rate limit - https://github.com/envoyproxy/ratelimit ??
Can one of the maintainers please comment. Looking for guidance, and possible availability of such a feature.