为了更快的定位您的问题，请提供以下信息，谢谢
【详述】be 节点挂掉
【背景】做过哪些操作？
【业务影响】
【StarRocks版本】2.5.6
【集群规模】例如：3fe（1 follower+2observer）+5be（fe与be混部）
be.out
query_id:7c17b58f-7edb-11ee-b7f7-48df372f334c, fragment_instance:7c17b58f-7edb-11ee-b7f7-48df372f335c
tracker:process consumption: 360522027384
tracker:query_pool consumption: 291538435927
tracker:load consumption: 20173840
tracker:metadata consumption: -10665853576
tracker:tablet_metadata consumption: 293115652
tracker:rowset_metadata consumption: 183881010
tracker:segment_metadata consumption: 1489802844
tracker:column_metadata consumption: -12632653082
tracker:tablet_schema consumption: 105778124
tracker:segment_zonemap consumption: 1183072987
tracker:short_key_index consumption: 272890985
tracker:column_zonemap_index consumption: 2963673750
tracker:ordinal_index consumption: -18546441088
tracker:bitmap_index consumption: 16251200
tracker:bloom_filter_index consumption: 119119392
tracker:compaction consumption: 33020896
tracker:schema_change consumption: 0
tracker:column_pool consumption: 7856372401
tracker:page_cache consumption: 1386366064
tracker:update consumption: 20528680296
tracker:chunk_allocator consumption: 2168301224
tracker:clone consumption: 0
tracker:consistency consumption: 0
*** Aborted at 1699519165 (unix time) try “date -d @1699519165” if you are using GNU date ***
PC: @ 0x31420f7 starrocks::Aggregator::~Aggregator()
*** SIGSEGV (@0xffffffff00000008) received by PID 16812 (TID 0x7fc0e3ecb700) from PID 8; stack trace: ***
@ 0x593cd22 google::(anonymous namespace)::FailureSignalHandler()
@ 0x7fc26a100630 (unknown)
@ 0x31420f7 starrocks::Aggregator::~Aggregator()
@ 0x2d5929a std::_Sp_counted_ptr_inplace<>::_M_dispose()
@ 0x2d599aa std::_Sp_counted_ptr_inplace<>::_M_dispose()
@ 0x2d3350a std::vector<>::~vector()
@ 0x2d5956d std::_Sp_counted_deleter<>::_M_dispose()
@ 0x2d181ca starrocks::pipeline::FragmentContext::~FragmentContext()
@ 0x2c0b1ca std::_Sp_counted_base<>::_M_release()
@ 0x2cf5831 starrocks::pipeline::QueryContext::~QueryContext()
@ 0x2c0b1ca std::_Sp_counted_base<>::_M_release()
@ 0x2cf5358 starrocks::pipeline::QueryContextManager::remove()
@ 0x2d11479 starrocks::pipeline::PipelineDriver::finalize()
@ 0x4f6ffbf starrocks::pipeline::GlobalDriverExecutor::_worker_thread()
@ 0x49656a2 starrocks::ThreadPool::dispatch_thread()
@ 0x496019a starrocks:
:supervise_thread()
@ 0x7fc26a0f8ea5 start_thread
@ 0x7fc2697138dd __clone
@ 0x0 (unknown)
start time: Thu Nov 9 16:43:20 CST 2023
这个大概率是已知问题 有类似的堆栈修复 麻烦您升级到最新的2.5.13版本吧 再进行下验证