-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Enhancement] add partition scan num limit when query internal olap table (backport #53747) #54353
Conversation
…able (#53747) Why I'm doing: when query big size internal olap table with full table scan or scan too many partitions, would cause BE/CN node high load, lead to cluster instability. What I'm doing: add a new FE session variable scan_olap_partition_num_limit to limit partition scan num when query internal olap table. (default value is 0, means no limitation) Signed-off-by: MatthewH00 <[email protected]> Signed-off-by: hmx <[email protected]> (cherry picked from commit a0a25b4) # Conflicts: # fe/fe-core/src/main/java/com/starrocks/qe/SessionVariable.java
Cherry-pick of a0a25b4 has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
@mergify[bot]: Backport conflict, please reslove the conflict and resubmit the pr |
Signed-off-by: Kevin Xiaohua Cai <[email protected]>
|
Refs StarRocks#54353, StarRocks#53747 Signed-off-by: Kevin Xiaohua Cai <[email protected]>
…able (backport StarRocks#53747) (StarRocks#54353) Signed-off-by: Kevin Xiaohua Cai <[email protected]> Co-authored-by: hmx <[email protected]> Co-authored-by: Kevin Xiaohua Cai <[email protected]>
Why I'm doing:
when query big size internal olap table with full table scan or scan too many partitions, would cause BE/CN node high load, lead to cluster instability.
What I'm doing:
add a new FE session variable
scan_olap_partition_num_limit
to limit partition scan num when query internal olap table.(default value is 0, means no limitation)
Fixes #issue
What type of PR is this:
Does this PR entail a change in behavior?
If yes, please specify the type of change:
Checklist: