Uh oh!
There was an error while loading. Please reload this page.
[feat](storage vault) Check storage vault connectivity for BE when starting - #51175
Conversation
Thearas
commented
May 23, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
swjtu-zhanglei
commented
May 23, 2025
run buildall |
doris-robot
commented
May 23, 2025
TPC-H: Total hot run time: 33831 ms |
doris-robot
commented
May 23, 2025
TPC-DS: Total hot run time: 192368 ms |
doris-robot
commented
May 23, 2025
ClickBench: Total hot run time: 29.11 s |
swjtu-zhanglei
commented
May 23, 2025
run buildall |
doris-robot
commented
May 23, 2025
TPC-H: Total hot run time: 33893 ms |
doris-robot
commented
May 23, 2025
TPC-DS: Total hot run time: 192794 ms |
doris-robot
commented
May 23, 2025
ClickBench: Total hot run time: 28.99 s |
hello-stephen
commented
May 23, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
May 23, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
swjtu-zhanglei
commented
May 28, 2025
run buildall |
doris-robot
commented
May 28, 2025
TPC-H: Total hot run time: 33682 ms |
doris-robot
commented
May 28, 2025
TPC-DS: Total hot run time: 192980 ms |
doris-robot
commented
May 28, 2025
ClickBench: Total hot run time: 29.71 s |
swjtu-zhanglei
commented
May 30, 2025
run buildall |
doris-robot
commented
May 30, 2025
TPC-H: Total hot run time: 33645 ms |
doris-robot
commented
May 30, 2025
TPC-DS: Total hot run time: 193220 ms |
doris-robot
commented
May 30, 2025
ClickBench: Total hot run time: 29.49 s |
hello-stephen
commented
May 30, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
May 30, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
swjtu-zhanglei
commented
Jun 3, 2025
run buildall |
doris-robot
commented
Jun 3, 2025
TPC-H: Total hot run time: 33862 ms |
doris-robot
commented
Jun 3, 2025
TPC-DS: Total hot run time: 193134 ms |
doris-robot
commented
Jun 3, 2025
ClickBench: Total hot run time: 29.2 s |
hello-stephen
commented
Jun 3, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
doris-robot
commented
Jun 24, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
Jun 24, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
PR approved by at least one committer and no changes requested. |
…arting (#51175) In storage vault mode during `BE` startup, if an aws role arn s3 vault is detected, we will check if the machine which `BE` deployed has been configured correctly. it will not allow `BE` starting if configuration is incorrect.
…arting (#51175) In storage vault mode during `BE` startup, if an aws role arn s3 vault is detected, we will check if the machine which `BE` deployed has been configured correctly. it will not allow `BE` starting if configuration is incorrect.
* 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
* #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
* #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
…r BE when starting apache#51175 (apache#52319) Cherry-picked from apache#51175 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
In storage vault mode during
BEstartup, if an aws role arn s3 vault is detected, we will check if the machine whichBEdeployed has been configured correctly. it will not allowBEstarting if configuration is incorrect.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)