-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[enhancement](cloud) support param to drop fe cluster not in safe time #50535
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:
|
|
run buildall |
gensrc/proto/cloud.proto
Outdated
| // for SQL mode rename cluster, rename to cluster name eq instance empty cluster name, need drop empty cluster | ||
| optional bool replace_if_existing_empty_target_cluster = 5; | ||
| // if true, check if drop_cluster op on sql type cluster is in safe time | ||
| optional bool safe_drop_on_sql_cluster = 6 [default = true]; |
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.
pls do not use default value, or there will be too many assumptions to be considered in the future.
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.
done
|
run buildall |
|
run cloud_ut |
TPC-H: Total hot run time: 34437 ms |
TPC-DS: Total hot run time: 192045 ms |
ClickBench: Total hot run time: 29.9 s |
deardeng
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 anyone and no changes requested. |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run cloud_p0 |
|
run cloud_ut |
BE Regression P0 && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run cloud_p0 |
1 similar comment
|
run cloud_p0 |
|
run p0 |
BE Regression P0 && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
TPC-H: Total hot run time: 33973 ms |
TPC-DS: Total hot run time: 192533 ms |
ClickBench: Total hot run time: 29.67 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run buildall |
TPC-H: Total hot run time: 33890 ms |
TPC-DS: Total hot run time: 185051 ms |
ClickBench: Total hot run time: 29.29 s |
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
|
run cloud_ut |
1 similar comment
|
run cloud_ut |
|
run cloud_p0 |
|
run cloudut |
|
reopen at #50680 |
What problem does this PR solve?
related pr: #45255
Currently, when the MS drop node/drop cluster api is called to the drop sql node/sql cluster, there is a 5 minute safe drop protection mechanism, but it is not necessary when destroying a newly created doris instance.
Allow bypassing the safe-time-check when calling the drop cluster api of meta service by setting the safe_derop_on_sql_cluster param to false
Add a configuration for the safe-time-check (default 5 minutes) to adjust this value
Api call example:
curl -X POST -H "Content-Type: text/plain" -d '{"instance_id": "123333", "cluster": {"cluster_name": "RESERVED_CLUSTER_NAME_FOR_SQL_SERVER", "cluster_id": "RESERVED_CLUSTER_ID_FOR_SQL_SERVER"}, "safe_drop_on_sql_cluster": "false"}' http://127.0.0.1:5000/MetaService/http/drop_cluster?token=xxxxxxxx
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)