-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[fix](be) Fix check_storage_vault deadlock
#52541
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
|
run buildall |
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
|
run performance |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
TPC-H: Total hot run time: 34005 ms |
TPC-DS: Total hot run time: 185892 ms |
ClickBench: Total hot run time: 29.83 s |
|
run buildall |
TPC-H: Total hot run time: 33629 ms |
TPC-DS: Total hot run time: 185057 ms |
ClickBench: Total hot run time: 29.35 s |
* apache#51175 introduced a deadlock problem: 1. the `sync_storage_vault()` func wait for heartbeat thread to set config::meta_service_endpoint 2. the heartbeat thread wait for the `sync_storage_vault()` func success to start
fe91340 to
637b2ae
Compare
|
run buildall |
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. |
|
PR approved by anyone and no changes requested. |
TPC-H: Total hot run time: 34647 ms |
TPC-DS: Total hot run time: 189799 ms |
ClickBench: Total hot run time: 30.43 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
* #51175 introduced a deadlock problem: 1. the `sync_storage_vault()` func wait for heartbeat thread to set config::meta_service_endpoint 2. the heartbeat thread wait for the `sync_storage_vault()` func success to start
* #51175 introduced a deadlock problem: 1. the `sync_storage_vault()` func wait for heartbeat thread to set config::meta_service_endpoint 2. the heartbeat thread wait for the `sync_storage_vault()` func success to start
Cherry-picked from #52541 Co-authored-by: Lei Zhang <zhanglei@selectdb.com>
…apache#52602) Cherry-picked from apache#52541 Co-authored-by: Lei Zhang <zhanglei@selectdb.com>
* apache#51175 introduced a deadlock problem: 1. the `sync_storage_vault()` func wait for heartbeat thread to set config::meta_service_endpoint 2. the heartbeat thread wait for the `sync_storage_vault()` func success to start
* apache#51175 introduced a deadlock problem: 1. the `sync_storage_vault()` func wait for heartbeat thread to set config::meta_service_endpoint 2. the heartbeat thread wait for the `sync_storage_vault()` func success to start
* apache#51175 introduced a deadlock problem: 1. the `sync_storage_vault()` func wait for heartbeat thread to set config::meta_service_endpoint 2. the heartbeat thread wait for the `sync_storage_vault()` func success to start
…pache#52603) Cherry-picked from apache#52541 Co-authored-by: Lei Zhang <zhanglei@selectdb.com>
the
sync_storage_vault()func wait for heartbeat thread to set config::meta_service_endpointthe heartbeat thread wait for the
sync_storage_vault()func success to startWhat 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)