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

Add "targetPartitionsPerWorker" setting for MSQ. #17048

Merged
merged 1 commit into from
Sep 13, 2024

Conversation

gianm
Copy link
Contributor

@gianm gianm commented Sep 12, 2024

As we move towards multi-threaded MSQ workers, it helps for parallelism to generate more than one partition per worker. That way, we can fully utilize all worker threads throughout all stages.

The default value is the number of processing threads. Currently, this is hard-coded to 1 for peons, but that is expected to change in the future.

As we move towards multi-threaded MSQ workers, it helps for parallelism
to generate more than one partition per worker. That way, we can fully
utilize all worker threads throughout all stages.

The default value is the number of processing threads. Currently, this
is hard-coded to 1 for peons, but that is expected to change in the future.
@github-actions github-actions bot added Area - Batch Ingestion Area - MSQ For multi stage queries - https://github.com/apache/druid/issues/12262 labels Sep 12, 2024
@gianm gianm merged commit d3f86ba into apache:master Sep 13, 2024
56 checks passed
@gianm gianm deleted the msq-target-partitions-per-worker branch September 13, 2024 23:01
gianm added a commit to gianm/druid that referenced this pull request Sep 14, 2024
clintropolis pushed a commit that referenced this pull request Sep 15, 2024
pranavbhole pushed a commit to pranavbhole/druid that referenced this pull request Sep 17, 2024
As we move towards multi-threaded MSQ workers, it helps for parallelism
to generate more than one partition per worker. That way, we can fully
utilize all worker threads throughout all stages.

The default value is the number of processing threads. Currently, this
is hard-coded to 1 for peons, but that is expected to change in the future.
pranavbhole pushed a commit to pranavbhole/druid that referenced this pull request Sep 17, 2024
@kfaraz kfaraz added this to the 31.0.0 milestone Oct 4, 2024
kfaraz pushed a commit to kfaraz/druid that referenced this pull request Oct 4, 2024
As we move towards multi-threaded MSQ workers, it helps for parallelism
to generate more than one partition per worker. That way, we can fully
utilize all worker threads throughout all stages.

The default value is the number of processing threads. Currently, this
is hard-coded to 1 for peons, but that is expected to change in the future.
kfaraz pushed a commit to kfaraz/druid that referenced this pull request Oct 4, 2024
kfaraz added a commit that referenced this pull request Oct 4, 2024
…) (#17074) (#17076) (#17077) (#17193) (#17243)

Backport the following patches for a clean backport of Dart changes
1. Add "targetPartitionsPerWorker" setting for MSQ. (#17048)
2. MSQ: Improved worker cancellation. (#17046)
3. Add "includeAllCounters()" to WorkerContext. (#17047)
4. MSQ: Include worker context maps in WorkOrders. (#17076)
5. TableInputSpecSlicer changes to support running on Brokers. (#17074)
6. Fix call to MemoryIntrospector in IndexerControllerContext. (#17066)
7. MSQ: Add QueryKitSpec to encapsulate QueryKit params. (#17077)
8. MSQ: Use task context flag useConcurrentLocks to determine task lock type (#17193)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area - Batch Ingestion Area - MSQ For multi stage queries - https://github.com/apache/druid/issues/12262
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants