-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
[fix](cloud) initial startup failure due to unconfigured metadata node #44696
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
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
run buildall |
TPC-H: Total hot run time: 32854 ms
|
TeamCity be ut coverage result: |
TPC-DS: Total hot run time: 197599 ms
|
ClickBench: Total hot run time: 31.81 s
|
836980c
to
73cb66b
Compare
run buildall |
TPC-H: Total hot run time: 33023 ms
|
TPC-DS: Total hot run time: 188865 ms
|
ClickBench: Total hot run time: 31.02 s
|
TeamCity be ut coverage result: |
73cb66b
to
ca0fc13
Compare
run buildall |
TeamCity be ut coverage result: |
TPC-H: Total hot run time: 32609 ms
|
TPC-DS: Total hot run time: 196529 ms
|
ClickBench: Total hot run time: 30.92 s
|
…metadata node #44696 (#46422) Cherry-picked from #44696 Co-authored-by: XLPE <[email protected]>
What problem does this PR solve?
Issue Number: close #44694
Problem Summary:
When the user does not manually configure the meta service endpoint in be.conf, during the first startup, the sync storage vault often occurs before the heartbeat. This results in std::call_once being called, which prevents the is_meta_service_endpoint_list from being updated subsequently.
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)