目前发现drop table 执行有时候快(秒级),有时候慢(5,6分钟),是否有参数可以提高删除速度?

为了更快的定位您的问题,请提供以下信息,谢谢
【详述】目前发现drop table 执行有时候快(秒级),有时候慢(5,6分钟),是否有参数可以提高删除速度?

【是否存算分离】是
【StarRocks版本】3.1.6
【集群规模】3fe+10be

执行快300s才删除完成,表内数据有 2427011
image

表结构:
CREATE TABLE ods_event_user_temp (
#user_id varchar(65533) NULL COMMENT “”,
#distinct_id varchar(65533) NULL COMMENT “”,
#create_time varchar(65533) NULL COMMENT “”,
#devicecode varchar(65533) NULL COMMENT “”,
#type varchar(65533) NULL COMMENT “”,
#time datetime NULL COMMENT “”,
#event varchar(65533) NULL COMMENT “”,
#uuid varchar(65533) NULL COMMENT “”,
#ip varchar(65533) NULL COMMENT “”,
#cpid bigint(20) NULL COMMENT “”,
#app_id varchar(65533) NULL COMMENT “”,
#product_id varchar(65533) NULL COMMENT “”,
#platform_id bigint(20) NULL COMMENT “”,
#channel_id varchar(65533) NULL COMMENT “”,
#sub_channel_id varchar(65533) NULL COMMENT “”,
#first_paid_time datetime NULL COMMENT “”,
#register_time datetime NULL COMMENT “”,
#agg_pay_money bigint(20) NULL COMMENT “”,
#agg_pay_count bigint(20) NULL COMMENT “”,
age decimal128(38, 9) NULL COMMENT “”,
#lastlogintime datetime NULL COMMENT “”,
#birthday datetime NULL COMMENT “”,
#total_money decimal128(38, 9) NULL COMMENT “”,
#regtime datetime NULL COMMENT “”,
#sex varchar(65533) NULL COMMENT “”,
#user_source_type varchar(65533) NULL COMMENT “”,
rx_total_money decimal128(38, 9) NULL COMMENT “”,
cp_userid decimal128(38, 9) NULL COMMENT “”,
reg_platform_name varchar(65533) NULL COMMENT “”,
reg_os varchar(65533) NULL COMMENT “”,
reg_os_version varchar(65533) NULL COMMENT “”,
reg_manufacturer varchar(65533) NULL COMMENT “”,
reg_device_model varchar(65533) NULL COMMENT “”,
login_platform_name varchar(65533) NULL COMMENT “”,
login_os varchar(65533) NULL COMMENT “”,
login_os_version varchar(65533) NULL COMMENT “”,
login_manufacturer varchar(65533) NULL COMMENT “”,
login_device_model varchar(65533) NULL COMMENT “”,
country varchar(65533) NULL COMMENT “”,
district varchar(65533) NULL COMMENT “”,
tf_firstlogin_adclickid varchar(65533) NULL COMMENT “”,
test_add_column decimal128(38, 9) NULL COMMENT “”,
country_code varchar(65533) NULL COMMENT “”,
province_code varchar(65533) NULL COMMENT “”,
user_id decimal128(38, 9) NULL COMMENT “”,
user_type decimal128(38, 9) NULL COMMENT “”,
first_pay_time datetime NULL COMMENT “”,
first_pay_type varchar(65533) NULL COMMENT “”,
first_pay_num decimal128(38, 9) NULL COMMENT “”,
user_res_358_lv decimal128(38, 9) NULL COMMENT “”,
user_res_358 decimal128(38, 9) NULL COMMENT “”,
user_res_17 decimal128(34, 0) NULL COMMENT “”,
user_res_15_all decimal128(34, 0) NULL COMMENT “”,
user_res_15 decimal128(34, 0) NULL COMMENT “”,
user_res_14 decimal128(34, 0) NULL COMMENT “”,
user_res_403 decimal128(38, 9) NULL COMMENT “”,
user_res_411 decimal128(38, 9) NULL COMMENT “”,
user_res_402 decimal128(38, 9) NULL COMMENT “”,
user_res_451 decimal128(38, 9) NULL COMMENT “”,
user_intcard_day decimal128(38, 9) NULL COMMENT “”,
user_intcard_time decimal128(38, 9) NULL COMMENT “”,
sum_login_duration decimal128(34, 0) NULL COMMENT “”,
sum_room__duration decimal128(34, 0) NULL COMMENT “”,
sum_room_bur decimal128(38, 9) NULL COMMENT “”,
sum_login_day decimal128(38, 9) NULL COMMENT “”,
sum_xzmoney_cost decimal128(34, 0) NULL COMMENT “”,
sum_money_cost decimal128(34, 0) NULL COMMENT “”,
corpid varchar(65533) NULL COMMENT “”,
accountId varchar(65533) NULL COMMENT “”,
account_name varchar(65533) NULL COMMENT “”,
unionid varchar(65533) NULL COMMENT “”,
union_name varchar(65533) NULL COMMENT “”,
external_userid varchar(65533) NULL COMMENT “”,
tf_firstlogin_date datetime NULL COMMENT “”,
user_bind_phone decimal128(38, 9) NULL COMMENT “”,
titles_type decimal128(38, 9) NULL COMMENT “”,
titles_time datetime NULL COMMENT “”,
user_certification decimal128(38, 9) NULL COMMENT “”,
sum_vip_value decimal128(38, 9) NULL COMMENT “”,
reg_time datetime NULL COMMENT “”,
tf_platform varchar(65533) NULL COMMENT “”,
tf_account_id varchar(65533) NULL COMMENT “”,
tf_plan_id varchar(65533) NULL COMMENT “”,
tf_advertising_id varchar(65533) NULL COMMENT “”,
tf_creative_id varchar(65533) NULL COMMENT “”,
tf_media_material_id varchar(65533) NULL COMMENT “”,
game_code_registered decimal128(38, 9) NULL COMMENT “”,
continent_ocean varchar(65533) NULL COMMENT “”,
country_chinese_name varchar(65533) NULL COMMENT “”,
mainland_region varchar(65533) NULL COMMENT “”,
province_name varchar(65533) NULL COMMENT “”,
city_code varchar(65533) NULL COMMENT “”,
city_name varchar(65533) NULL COMMENT “”,
district_code varchar(65533) NULL COMMENT “”,
district_name varchar(65533) NULL COMMENT “”,
carrier_name varchar(65533) NULL COMMENT “”,
country_english_name varchar(65533) NULL COMMENT “”,
country_code_2_letters varchar(65533) NULL COMMENT “”,
longitude varchar(65533) NULL COMMENT “”,
latitude varchar(65533) NULL COMMENT “”,
ad_activity varchar(65533) NULL COMMENT “”,
#created_at datetime NULL COMMENT “”,
#rx_nickname varchar(65533) NULL COMMENT “”,
#rx_avatar varchar(65533) NULL COMMENT “”,
#rx_cp_totalmoney decimal128(38, 9) NULL COMMENT “”,
#rx_cp_totalcurrency varchar(65533) NULL COMMENT “”,
#rx_lastrecharge_time varchar(65533) NULL COMMENT “”,
#rx_lastrecharge_money decimal128(38, 9) NULL COMMENT “”,
#rx_lastrecharge_currency varchar(65533) NULL COMMENT “”,
#rx_phone varchar(65533) NULL COMMENT “”,
#rx_email varchar(65533) NULL COMMENT “”,
#rx_region varchar(65533) NULL COMMENT “”,
#rx_lastlogin_region varchar(65533) NULL COMMENT “”,
#rx_lastlogin_method varchar(65533) NULL COMMENT “”,
#rx_lastlogin_channel varchar(65533) NULL COMMENT “”,
#rx_lastlogin_devicecode varchar(65533) NULL COMMENT “”,
#rx_account_status varchar(65533) NULL COMMENT “”,
#rx_account_suspdays varchar(65533) NULL COMMENT “”,
#rx_account_suspreason varchar(65533) NULL COMMENT “”,
#rx_account varchar(65533) NULL COMMENT “”,
#rx_regregion varchar(65533) NULL COMMENT “”,
#rx_preshare_userid varchar(65533) NULL COMMENT “”,
#rx_realname varchar(65533) NULL COMMENT “”,
#rx_sex decimal128(38, 9) NULL COMMENT “”,
#rx_idcard varchar(65533) NULL COMMENT “”,
#rx_lastlogin_ip varchar(65533) NULL COMMENT “”,
#rx_account_ban_start datetime NULL COMMENT “”,
#rx_account_ban_end datetime NULL COMMENT “”,
rx_total_money_p decimal128(38, 9) NULL COMMENT “”,
#zhubo boolean NULL COMMENT “”,
#zhubo_product varchar(65533) NULL COMMENT “”,
#zhubo_game varchar(65533) NULL COMMENT “”,
#zhubo_commerce varchar(65533) NULL COMMENT “”,
#zhubo_operate varchar(65533) NULL COMMENT “”,
#zhubo_institution varchar(65533) NULL COMMENT “”,
#zhubo_platform varchar(65533) NULL COMMENT “”,
#zhubo_union varchar(65533) NULL COMMENT “”,
#zhubo_platform_id varchar(65533) NULL COMMENT “”,
#zhubo_platform_name varchar(65533) NULL COMMENT “”,
#rx_totalcurrency varchar(65533) NULL COMMENT “”,
#rx_lastlogin_time datetime NULL COMMENT “”,
#rx_cancel_commit_time datetime NULL COMMENT “”,
#rx_cancel_time datetime NULL COMMENT “”,
#zhubo_group_id varchar(65533) NULL COMMENT “”,
#zhubo_cp_user_id varchar(65533) NULL COMMENT “”
) ENGINE=OLAP
DUPLICATE KEY(#user_id)
COMMENT “OLAP”
DISTRIBUTED BY RANDOM
PROPERTIES (
“replication_num” = “1”,
“datacache.enable” = “true”,
“storage_volume” = “builtin_storage_volume”,
“enable_async_write_back” = “false”,
“enable_persistent_index” = “false”,
“compression” = “LZ4”
);

请问有drop比较慢的时候,leader fe的fe.log日志吗?

大佬,私信发你了,3个fe,不记得是哪一个,我都把日志给发过去了,10点到12点之间的

大佬,私信发你了,3个fe,不记得是哪一个,我都把日志给发过去了,10点到12点之间的日志

排查下来发现应该是be执行慢导致fe与be通信超时导致的,这个问题后续版本会优化下。
排查方式:

  1. 在fe leader节点的fe.log搜索被drop的表,对应时间存在如下日志
    2023-12-29 10:10:27,562 INFO (starrocks-mysql-nio-pool-334|333127) [Database.unprotectDropTable():540] finished dropping table[table_name_temp] in db[rxxx_bd_xxx], tableId: 17159744
  2. 在fe leader节点的fe.log中继续搜索当前线程号,starrocks-mysql-nio-pool-334|333127,看后续这个线程在做什么
    2023-12-29 10:15:27,634 WARN (starrocks-mysql-nio-pool-334|333127) [DeleteLakeTableTask.removePartitionDirectory():107] Fail to execute removal of s3://xxxxx on node xx.xx.xxx.xx: A error occurred: errorCode=62 errorMessage:method request time out, please check ‘onceTalkTimeout’ property. current value is:300000(MILLISECONDS) correlationId:4199387 timeout with bound channel =>[id: 0x2c61f1f5, L:/$leder_fe_ip:40784 - R:/$be_ip:8060]
  3. 到$be_ip节点上检查be.INFO日志