Skip to content
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 distributed mode does not fetch from storage gateways #7757

Open
hanem100k opened this issue Sep 18, 2024 · 5 comments
Open

Query distributed mode does not fetch from storage gateways #7757

hanem100k opened this issue Sep 18, 2024 · 5 comments

Comments

@hanem100k
Copy link

hanem100k commented Sep 18, 2024

Query, store gateway

Thanos, Prometheus and Golang version used:
Thanos version 0.26.1

Object Storage Provider:
Azure blob store

What happened:
Having a set of receivers and sharded store gateways. Whenever query distributed mode is enabled, data will only be returned from receivers but not stores.

Removing query.mode=distributed from arguments solves the issue.

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):
It is reproducible 100% when you query for a time range that exceeds your receivers.

Metrics with distribution enabled:
image

Metrics without distribution enabled:
image

@MichaHoffmann
Copy link
Contributor

Note:

func (r *remoteEngine) MinT() int64 {
likely the MinT() computation is off for usecases where we have [sidecar,receiver,..]+storagegw endpoints on same remote engine.

@fpetkovski
Copy link
Contributor

@hanem100k can you try attaching a separate querier to store gateways?

@hanem100k
Copy link
Author

I do have a Top level [QFE] -> [Q] -> Leaf [Q] -> [receivers, stores]

There is a single Query in the top layer and there are N leafs.

If I go into the leaf Querier directly, it returns ok from stores as well as receivers.

@fpetkovski

can you try attaching a separate querier to store gateways?

Do you mean that I should retry the distributed mode by having a Querier for stores only and one for receivers only?

@fpetkovski
Copy link
Contributor

Actually we are going to fix this configuration with @MichaHoffmann soon, so let's wait for the new patch release.

@yeya24
Copy link
Contributor

yeya24 commented Nov 11, 2024

@fpetkovski Is this issue already fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants