Uh oh!
There was an error while loading. Please reload this page.
[enhancement](cloud) support param to drop fe cluster not in safe time - #50535
[enhancement](cloud) support param to drop fe cluster not in safe time#50535xy720 wants to merge 5 commits into
Conversation
Thearas
commented
Apr 29, 2025
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
xy720
commented
Apr 29, 2025
run buildall |
| // 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.
pls do not use default value, or there will be too many assumptions to be considered in the future.
xy720
commented
Apr 29, 2025
run buildall |
xy720
commented
Apr 29, 2025
run cloud_ut |
doris-robot
commented
Apr 29, 2025
TPC-H: Total hot run time: 34437 ms |
doris-robot
commented
Apr 29, 2025
TPC-DS: Total hot run time: 192045 ms |
doris-robot
commented
Apr 29, 2025
ClickBench: Total hot run time: 29.9 s |
PR approved by anyone and no changes requested. |
hello-stephen
commented
Apr 29, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
xy720
commented
Apr 29, 2025
run cloud_p0 |
xy720
commented
Apr 29, 2025
run cloud_ut |
hello-stephen
commented
Apr 29, 2025
BE Regression P0 && UT Coverage ReportIncrement line coverage Increment coverage report
|
xy720
commented
Apr 29, 2025
run cloud_p0 |
1 similar comment
xy720
commented
Apr 29, 2025
run cloud_p0 |
xy720
commented
Apr 29, 2025
run p0 |
hello-stephen
commented
Apr 29, 2025
BE Regression P0 && UT Coverage ReportIncrement line coverage Increment coverage report
|
xy720
commented
May 6, 2025
run buildall |
doris-robot
commented
May 6, 2025
TPC-H: Total hot run time: 33973 ms |
doris-robot
commented
May 6, 2025
TPC-DS: Total hot run time: 192533 ms |
doris-robot
commented
May 6, 2025
ClickBench: Total hot run time: 29.67 s |
doris-robot
commented
May 6, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
May 6, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
xy720
commented
May 7, 2025
run buildall |
doris-robot
commented
May 7, 2025
TPC-H: Total hot run time: 33890 ms |
doris-robot
commented
May 7, 2025
TPC-DS: Total hot run time: 185051 ms |
doris-robot
commented
May 7, 2025
ClickBench: Total hot run time: 29.29 s |
hello-stephen
commented
May 7, 2025
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
hello-stephen
commented
May 7, 2025
BE Regression && UT Coverage ReportIncrement line coverage Increment coverage report
|
xy720
commented
May 7, 2025
run cloud_ut |
1 similar comment
xy720
commented
May 7, 2025
run cloud_ut |
xy720
commented
May 7, 2025
run cloud_p0 |
xy720
commented
May 7, 2025
run cloudut |
xy720
commented
May 8, 2025
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)