[fix](meta) set parallel_pipeline_task_num when upgrading from 1.2 to 2.0 #22618
Conversation
This file contains hidden or 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
morningman
force-pushed
the
upgrade_parallel
branch
from
2f87e1b to
a53393c
Compare
Contributor
Author
|
run buildall |
morningman
changed the title
Contributor
|
(From new machine)TeamCity pipeline, clickbench performance test result: |
github-actions
bot
added
the
approved
Contributor
|
PR approved by at least one committer and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
Contributor
|
PR approved by anyone and no changes requested. |
xiaokang
pushed a commit
that referenced
this pull request
Aug 5, 2023
Gabriel39
pushed a commit
to Gabriel39/incubator-doris
that referenced
this pull request
Aug 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Proposed changes
follow #22617.
When upgrading from 1.2 to 2.0, we need to make sure that the parallelism of query remain unchanged
when switch to pipeline engine, otherwise it may impact the load of entire cluster
because the default parallelism of pipeline engine is higher than previous version.
so set parallel_pipeline_task_num to parallel_fragment_exec_instance_num
Further comments
If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...