-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[improve](cloud-mow) make the waiting time on getDeleteBitmapUpdateLock more reasonable #40341
Conversation
…ck more reasonable
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
run buildall |
TPC-H: Total hot run time: 38004 ms
|
TPC-DS: Total hot run time: 193599 ms
|
ClickBench: Total hot run time: 31.41 s
|
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. |
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
…ck more reasonable (#40341) now the expired time of mow delete bitmap lock on ms is 60s, so fe should try to wait at most 60s to getDeleteBitmapUpdateLock.
now the expired time of mow delete bitmap lock on ms is 60s, so fe should try to wait at most 60s to getDeleteBitmapUpdateLock.