-
Notifications
You must be signed in to change notification settings - Fork 820
Proposal for distributed query execution #6789
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
base: master
Are you sure you want to change the base?
Proposal for distributed query execution #6789
Conversation
Signed-off-by: 🌲 Harry 🌊 John 🏔 <johrry@amazon.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the great work. I like this proposal.
This looks great! I cannot wait to see it working! :D:D:D |
Signed-off-by: 🌲 Harry 🌊 John 🏔 <johrry@amazon.com>
ea50781
to
37692c4
Compare
|
||
#### Co-ordinated Execution | ||
|
||
The querier assigned the **root fragment** also plays the role of **coordinator**. The co-ordinator will |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The root querier will call Series
and Next
to the child querier. Those requests will also specify the logical plan ID or some sort of request ID so the child querier finds out the actual plan?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. Yes, we need to refer fragments by ID.
|
||
#### Inefficient Merging | ||
|
||
Merging results in the query-frontend—which isn’t shuffle-sharded — makes it a single point of failure. Poison queries can OOM all query-frontends, impacting availability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could we define what "poison queries" are?
What this PR does:
Submits a proposal for distributed query execution in Cortex using Thanos PromQL engine.
Which issue(s) this PR fixes:
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]