be节点 crash

💬 StarRocks 用户问答
#1

为了更快的定位您的问题，请提供以下信息，谢谢
【详述】问题详细描述
没有 query id 也没有异常日志 dmesg -T 也没有 比较奇怪 不知道为什么crash

start time: Fri Jul 4 16:22:13 CST 2025, server uptime: 16:22:13 up 22 days, 1:13, 0 users, load average: 15.77, 27.27, 19.96
branch-3.3.15 RELEASE (build c501f88)
query_id:00000000-0000-0000-0000-000000000000, fragment_instance:00000000-0000-0000-0000-000000000000
tracker:process consumption: 2504216944
tracker:jemalloc_metadata consumption: 142245040
tracker:query_pool consumption: 120944856
tracker:query_pool/connector_scan consumption: 0
tracker:load consumption: 0
tracker:metadata consumption: 968446674
tracker:tablet_metadata consumption: 827420411
tracker:rowset_metadata consumption: 139022438
tracker:segment_metadata consumption: 251331
tracker:column_metadata consumption: 1752494
tracker:tablet_schema consumption: 32514803
tracker:segment_zonemap consumption: 171672
tracker:short_key_index consumption: 12352
tracker:column_zonemap_index consumption: 302206
tracker:ordinal_index consumption: 495568
tracker:bitmap_index consumption: 0
tracker:bloom_filter_index consumption: 0
tracker:compaction consumption: 0
tracker:schema_change consumption: 0
tracker:column_pool consumption: 0
tracker:page_cache consumption: 729952
tracker:jit_cache consumption: 1720
tracker:update consumption: 80445841
tracker:chunk_allocator consumption: 0
tracker:passthrough consumption: 0
tracker:clone consumption: 0
tracker:consistency consumption: 0
tracker:datacache consumption: 0
tracker:replication consumption: 0
*** Aborted at 1751617652 (unix time) try “date -d @1751617652” if you are using GNU date ***
PC: @ 0x79d354c starrocks::pipeline::FragmentExecutor::_prepare_query_ctx(starrocks::ExecEnv*, starrocks::pipeline::UnifiedExecPlanFragmentParams const&)
*** SIGSEGV (@0x10) received by PID 25 (TID 0x7f49245dd640) from PID 16; stack trace: ***
@ 0x7f4a725cfee8 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x99ee7)
@ 0x9adb869 google::(anonymous namespace)::FailureSignalHandler(int, siginfo_t*, void*)
@ 0x7f4a72578520 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x4251f)
@ 0x79d354c starrocks::pipeline::FragmentExecutor::_prepare_query_ctx(starrocks::ExecEnv*, starrocks::pipeline::UnifiedExecPlanFragmentParams const&)
@ 0x79d7c06 starrocks::pipeline::FragmentExecutor::prepare(starrocks::ExecEnv*, starrocks::TExecPlanFragmentParams const&, starrocks::TExecPlanFragmentParams const&)
@ 0x855f9bb starrocks::PInternalServiceImplBasestarrocks::PInternalService::_exec_plan_fragment_by_pipeline(starrocks::TExecPlanFragmentParams const&, starrocks::TExecPlanFragmentParams const&)
@ 0x85657c5 starrocks::PInternalServiceImplBasestarrocks::PInternalService::_exec_plan_fragment(brpc::Controller*, starrocks::PExecPlanFragmentRequest const*)
@ 0x856ffff starrocks::PInternalServiceImplBasestarrocks::PInternalService::_exec_plan_fragment(google::protobuf::RpcController*, starrocks::PExecPlanFragmentRequest const*, starrocks::PExecPlanFragmentResult*, google::protobuf::Closure*)
@ 0x4fa264d starrocks::PriorityThreadPool::work_thread(int)
@ 0x9a8e39b thread_proxy
@ 0x7f4a725caac3 (/usr/lib/x86_64-linux-gnu/libc.so.6+0x94ac2)
@ 0x7f4a7265ba04 clone
[1751617653.111][thread:139952119469632] je_mallctl execute purge success
[1751617653.111][thread:139952119469632] je_mallctl execute dontdump success
start time: Fri Jul 4 16:31:28 CST 2025, server uptime: 16:31:28 up 22 days, 1:23, 0 users, load average: 15.39, 31.08, 24.93

【背景】做过哪些操作？
【业务影响】
【是否存算分离】
【StarRocks版本】例如：1.18.2
【集群规模】例如：3fe（1 follower+2observer）+5be（fe与be混部）
【机器信息】CPU虚拟核/内存/网卡，例如：48C/64G/万兆
【联系方式】为了在解决问题过程中能及时联系到您获取一些日志信息，请补充下您的联系方式，例如：社区群4-小李或者邮箱，谢谢
【附件】

京ICP备2022026421号-1