feat: shuffle segments during distributed pruning #8793
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
mergify
bot
added
the
pr-feature
dantengsky
force-pushed
the
feat-shuffle-segments
branch
from
e10cd64
to
427d8c0
Compare
|
If the segment number is too slow (less than query nodes), the FuseLazyPartInfo seems too lazy to schedule. |
BohuTANG
approved these changes
Nov 15, 2022
This was referenced Nov 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I hereby agree to the terms of the CLA available at: https://databend.rs/dev/policies/cla/
Summary
shuffle segment before distributed pruning, to mitigate potential data skew
has(segment_path) % number_of_nodesso that segments are shuffled, and the same segment is likely(but not assured) to be sent to the same query node (assuming stable membership of the query cluster).
Closes #issue