-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Connect sidecar proxy upstream config connect_timeout_ms does not work #11603
Comments
Hey @tmiroslav , I believe for the timeouts to work it has to be set on the proxy level ( |
Hi @Amier3 Thank you! BR, |
Hi @Amier3 It's no better after adding
Still, I am getting in the logs something like: Where I can see that it still timeouts after 5s!? Thank you! |
Hi @Amier3 Any advice what I should do next? Should I go for Consul/Envoy upgrade maybe for this to make working? Thanx! |
Hey @tmiroslav Apologies for the delayed response! After looking into this issue a bit more, I realized that i'd need to pull in some of the engineering team to help figure out how to fix this and if an upgrade was required. Due to the holidays that were quickly approaching, it was hard to find the bandwidth to dig deep into this in December. Are you still experiencing this issue and did you end up upgrading to try to fix it? |
Also, it'd help a lot if you can provide us with an envoy config dump using |
@tmiroslav maybe have a look at my comment here: #6382 (comment) - I suspect the section on Upstream Request Timeouts is what you're running into, as it's not something that has been addressed yet. I have a couple of proposed options on that PR (including one you can use today with a service-router, and another which disables the upstream timeouts entirely, which we do with a custom build of Consul presently). |
When filing a bug, please include the following headings if possible. Any example text in this template can be deleted.
It ls failing to setup connection timeout in upstream config per docs here
A paragraph or two about the issue you're experiencing:
I am facing timeouts every time upstream service that my service is connecting to is not responding in 5s. This is too low for my use case and I want to extend this timeout to 10s. But when setup proper connect_timeout_ms in upstream config, I realize that my service still timeouts after 5s. So, my config change in upstream proxy config is not applied.
Reproduction Steps
Steps to reproduce this issue, eg:
This is my service definition file:
Consul info for both Client and Server
Consul v1.8.3 Envoy 1.14.2
Client info:
Server info:
Operating system and Environment details
more /etc/os-release
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"
CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"
The text was updated successfully, but these errors were encountered: