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

Uncertain about partial response propagation #7882

Open
wiardvanrij opened this issue Nov 4, 2024 · 0 comments
Open

Uncertain about partial response propagation #7882

wiardvanrij opened this issue Nov 4, 2024 · 0 comments

Comments

@wiardvanrij
Copy link
Member

I'm not sure if this is a bug or not, but I suspect it might be since I'm experiencing this issue.

To explain things better, I've made this 'diagram', which is actually a simplification of how our stack looks like.

image

To explain the setup:

  • There is some chaining involved
  • One querier chains to another querier, where that second querier access 'B' stores
  • In reality, there is even more chaining involved, where we have this 'TLS' querier and one without, and we chain that into another querier - Yet I think for this question, it's not relevant.

My ask here is:

  • If one of the B stores, let's say xB, is down. It should provide that querier with a partial response.
  • Does this propagate correctly to the initial querier (on the left) as well?

Main reason I'm asking, is that I had this case were partial data was cached by the query frontend cache. Which simply can never happen because we have strict endpoints. Therefore I'm assuming there is a bug somewhere.

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

1 participant