-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](cloud) fix corner case when warm up data larger than cache capacity #49050
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
Conversation
…city when warm up target table's first partition is larger cache capacity of the cluster/compute group, the deleted code will break and leave warmUpTotalFileCache zero, resulting no error&warning but 0 batch size. this commit will warn user this situation and allow user use FORCE warm up to load partial data into the file cache. Signed-off-by: zhengyu <zhangzhengyu@selectdb.com>
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
fe/fe-core/src/main/java/org/apache/doris/cloud/CacheHotspotManager.java
Show resolved
Hide resolved
TPC-H: Total hot run time: 32548 ms |
TPC-DS: Total hot run time: 186250 ms |
ClickBench: Total hot run time: 31.19 s |
|
run buildall |
TPC-H: Total hot run time: 34149 ms |
TPC-DS: Total hot run time: 193150 ms |
ClickBench: Total hot run time: 31.38 s |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
dataroaring
left a comment
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.
LGTM
…city (#49050) when warm up target table's first partition is larger cache capacity of the cluster/compute group, the deleted code will break and leave warmUpTotalFileCache zero, resulting no error&warning but 0 batch size. this commit will warn user this situation and allow user use FORCE warm up to load partial data into the file cache.
…city (apache#49050) when warm up target table's first partition is larger cache capacity of the cluster/compute group, the deleted code will break and leave warmUpTotalFileCache zero, resulting no error&warning but 0 batch size. this commit will warn user this situation and allow user use FORCE warm up to load partial data into the file cache.
when warm up target table's first partition is larger cache capacity of the cluster/compute group, the deleted code will break and leave warmUpTotalFileCache zero, resulting no error&warning but 0 batch size.
this commit will warn user this situation and allow user use FORCE warm up to load partial data into the file cache.
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)