-
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
[Query] Partial response doesn't work if one of stores returned timeout #835
Comments
Well, is it because the request to one of the stor actually took too long to wait, and either your client or Thanos Query server timeout killed the request? (: So it's not partial erorr - whole request took too long, even though the root cause was one slow store. So now is the question what would you expect in this case? (: |
Yes, In this case Thanos Query killed request, but some stores already returned data. I think this case should not be different with behaviour if one of stores is down at all |
@bwplotka any ideas?) |
Hm.. yes, as long as I am fine to accept PR with your idea though to have this internal timeout to be configurable for Thanos Querier 👍 |
so what #895 is adding? ;p |
Moving discussion to #1453 |
Hi, Thanos team!
What happened:
Thanos Query returns error (context deadline exceeded) if one of requested stores failed with timeout.
Partial response parameter is enabled.
Expected behaviour:
Thanos returns part of successfully fetched data and warning that one of stores failed.
In the same time there is an other case: if one of stores is not available at all (process is not running e.g.) Thanos Query returns data partially and warning.
It seems that behaviour should be the same in both cases.
@bwplotka what do you think?
Thanos v0.2.1
The text was updated successfully, but these errors were encountered: