-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
#4657 broke query -> sidecar communication #4688
Comments
9090 is the Prometheus port, not the thanos-sidecar port. |
Ok so I don't reproduce anymore ... I'm sorry for the annoyance. |
It's ok 👍 no worries 🤗 |
if the port 9090 is point to sidecar correctly. I think the error log is produced when sidecar is up but prometheus is not ready,so query timeout by context deadline exceeded. |
9090 was the port on the reverse proxy which was forwarding on 10901. The mistery lies elsewhere ... Sorry again to have wasted your time. |
No worries, good we found the issue and it's not a release blocker! 🤗 |
Thanos, Prometheus and Golang version used:
Thanos: HEAD
Go: 1.17.1
Object Storage Provider:
S3
What happened:
While testing #4667 I merged the main branch into it locally and it broke the communication between my thanos query and thanos sidecar.
I bisected and reverting #4657 resolved the issue.
I don't know if it is relevant but I have a traefik reverse proxy between thanos-query and the incriminated thanos-sidecar.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Anything else we need to know:
The text was updated successfully, but these errors were encountered: