2.0.0版本，我在log 下找了一圈，没找到 BE节点挂掉时的真正原因的日志。
BE节点是早上6点50左右挂掉了。请问是在哪个文件里面能找到？
be.out 里面有
start time: Mon May 15 14:09:52 CST 2023
tcmalloc: large alloc 1109852160 bytes == 0x604bb0000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16ffc84 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fb751c7bea5
tcmalloc: large alloc 1438605312 bytes == 0x6b3770000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16ffc84 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fb751c7bea5
tcmalloc: large alloc 2147491840 bytes == 0x999ce2000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x2134e05 0x225f8c2 0x1ffbb96 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fb751c7bea5
tcmalloc: large alloc 2147483648 bytes == 0xa354e8000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x1ffbb96 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fb751c7bea5
tcmalloc: large alloc 2147450880 bytes == 0x999ce2000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fb751c7bea5
tcmalloc: large alloc 2147483648 bytes == 0xd9b90a000 @ 0x4c664d9 0x4de40dc 0x4de443e 0x1bf54b6 0x1bd54fd 0x1b86bd3 0x1b4a6e7 0x20030e8 0x25b1fd6 0x25b2125 0x2501e73 0x233a20d 0x1ffc8fd 0x225f8c2 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fb751c7bea5
*** Aborted at 1689130812 (unix time) try “date -d @1689130812” if you are using GNU date ***
PC: @ 0x7fb7510d13b8 __memcpy_ssse3
*** SIGSEGV (@0x0) received by PID 603616 (TID 0x7fb711382700) from PID 0; stack trace: ***
@ 0x3397d22 google::(anonymous namespace)::FailureSignalHandler()
@ 0x7fb751c83630 (unknown)
@ 0x7fb7510d13b8 __memcpy_ssse3
@ 0x25b1fe4 starrocks::vectorized::DistinctAggregateState<>::deserialize_and_merge()
@ 0x25b2125 starrocks::vectorized::TDistinctAggregateFunction<>::merge()
@ 0x2501e73 starrocks::vectorized::NullableAggregateFunctionBase<>::merge_batch()
@ 0x233a20d starrocks::Aggregator::compute_batch_agg_states()
@ 0x1ffc8fd starrocks::vectorized::AggregateBlockingNode::open()
@ 0x225f8c2 starrocks::vectorized::ProjectNode::open()
@ 0x1baef8b starrocks::PlanFragmentExecutor::_open_internal_vectorized()
@ 0x1bafc17 starrocks::PlanFragmentExecutor::open()
@ 0x1b52052 starrocks::FragmentExecState::execute()
@ 0x1b55e65 starrocks::FragmentMgr::exec_actual()
@ 0x1c80bb9 starrocks::ThreadPool::dispatch_thread()
@ 0x1c8f1b5 starrocks:
:supervise_thread()
@ 0x7fb751c7bea5 start_thread
@ 0x7fb75108096d __clone
@ 0x0 (unknown)
start time: Wed Jul 12 11:01:02 CST 2023
tcmalloc: large alloc 1445478400 bytes == 0x9d6b2a000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16ffc84 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fe78a06aea5
tcmalloc: large alloc 2077433856 bytes == 0xc62dfc000 @ 0x4c664d9 0x4de40dc 0x1bef4ba 0x4d34785 0x16ffc84 0x16f8e36 0x213d0ee 0x21349f5 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x2134e05 0x225f8c2 0x1baef8b 0x1bafc17 0x1b52052 0x1b55e65 0x1c80bb9 0x1c8f1b5 0x7fe78a06aea5
start time: Fri Jul 28 06:51:02 CST 2023
这咋看？？
这个应该是触发了一个已知的bug，可以升到对应的最新release