-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](cloud-mow) Make some timeout about mow more reasonable #46365
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
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run buildall |
TPC-H: Total hot run time: 33516 ms |
TPC-DS: Total hot run time: 189816 ms |
ClickBench: Total hot run time: 32.31 s |
|
TeamCity be ut coverage result: |
|
run buildall |
TPC-H: Total hot run time: 32813 ms |
TPC-DS: Total hot run time: 197928 ms |
ClickBench: Total hot run time: 31.27 s |
|
TeamCity be ut coverage result: |
|
run buildall |
TPC-H: Total hot run time: 32461 ms |
TPC-DS: Total hot run time: 197719 ms |
ClickBench: Total hot run time: 31.28 s |
|
TeamCity be ut coverage result: |
|
run buildall |
|
@zhannngchen take a look plz |
TPC-H: Total hot run time: 32591 ms |
TPC-DS: Total hot run time: 195915 ms |
ClickBench: Total hot run time: 31.39 s |
|
TeamCity be ut coverage result: |
zhannngchen
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
TPC-H: Total hot run time: 32552 ms |
TPC-DS: Total hot run time: 185149 ms |
ClickBench: Total hot run time: 30.27 s |
|
TeamCity be ut coverage result: |
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
|
PR approved by at least one committer and no changes requested. |
Now some timeout config is not suitable for high concurrency loading on Mow table, which may lead to frequent lock timeouts.
…46365) Now some timeout config is not suitable for high concurrency loading on Mow table, which may lead to frequent lock timeouts.
apache#47295) after pr apache#46365, commit mow table may cost 1800s at most (rpc timeout*retry times), so the delete bitmap cache expiration time should be set to 1800s.This cache will be automatically deleted after the loading task is completed. Only when task fails, this cache will be clean in background.
…apache#47666) pr apache#46365 adjust timeout about mow load, thers is no need so much retry times, can reduce to 5.
…46365) Now some timeout config is not suitable for high concurrency loading on Mow table, which may lead to frequent lock timeouts.
apache#47295) after pr apache#46365, commit mow table may cost 1800s at most (rpc timeout*retry times), so the delete bitmap cache expiration time should be set to 1800s.This cache will be automatically deleted after the loading task is completed. Only when task fails, this cache will be clean in background.
…apache#47666) pr apache#46365 adjust timeout about mow load, thers is no need so much retry times, can reduce to 5.
Now some timeout config is not suitable for high concurrency loading on Mow table, which may lead to frequent lock timeouts.
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)