-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[Fix](cloud) Cloud enable fe deploy mode from master-observers to multi-followers #45255
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:
|
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run buildall |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
TPC-H: Total hot run time: 39925 ms |
|
run cloudut |
TPC-DS: Total hot run time: 197298 ms |
ClickBench: Total hot run time: 33.39 s |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
run buildall |
|
clang-tidy review says "All clean, LGTM! 👍" |
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
|
run buildall |
|
PR approved by at least one committer and no changes requested. |
TPC-H: Total hot run time: 32560 ms |
TPC-DS: Total hot run time: 197888 ms |
ClickBench: Total hot run time: 31.71 s |
Hastyshell
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
…ti-followers (apache#45255) IN CLOUD 1. add some cloud metaservice api regression test 2. prohibit one node add to multi cluster repeatedly 3. supports switching from master observer mode to multi follower mode, and compatible with upgrading from existing master-observers deployment mode to multi-follwers mode 4. when adding an FE node(add fe cluster, add fe node), there is a 5-minute protection time and the FE node cannot be droped(drop fe cluster, drop fe node) 5. drop the node. If the node cannot be found, an error will occur and the code will return 404 instead of the previous silent processing 6. If the MS node starts with 127.0.0.1 IP and the `prohibit_use_loopback_addresses` is set to true(default), the MS node will not be able to start, ms log will find `enable check prohibit use loopback addr, but localhost=127.0.0.1, so exit(-1)`
### What problem does this PR solve? Related PR: #45255
### What problem does this PR solve? Related PR: #45255
) ### What problem does this PR solve? Related PR: apache#45255
) ### What problem does this PR solve? Related PR: apache#45255
What problem does this PR solve?
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
IN CLOUD
prohibit_use_loopback_addressesis set to true(default), the MS node will not be able to start, ms log will findenable check prohibit use loopback addr, but localhost=127.0.0.1, so exit(-1)Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)