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
Thanos receive context deadline exceeded: Permanent error: Post \"http://obs-thanos-receive.xxxsvc.cluster.local:19291/api/v1/receive\": context deadline exceeded #7257
Comments
Maybe you could try the version from |
@GiedriusS I have tried with main-2024-04-03-f80fd94, I am still seeing following error
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanos, Prometheus and Golang version used:
Thanos: v0.34.1
Object Storage Provider: MinIO object storage
What happened:
Our pipeline has a OpenTelemetry collector in front of the thanos Receiver stacks.
We performed load testing with TPS (Transaction Per Second)=2500 using k6 testing tool, we observed that there are significant data drops, and errors from Opentelemetry collector shows some context deadline timeout issue, e.g.
However, we are not able to identify any errors from the receiver logs except some out-of-order samples, which is expected.
We don't have any limits configured on Thanos receiver, and as far as we are concerned, By default all the limits and gates are disabled on receivers.
Receiver config:
Receiver distributor config
Hashring
It works perfectly with TPS=1500
What you expected to happen:
There should be minimal data drops with TPS=2500 as we have similar load testing against Prometheus before, which works fine.
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: