【详述】集群be内存突然升高，有一台be crash
【背景】无
【业务影响】 be crash 稳定性变差
【StarRocks版本】例如：2.4.0
【集群规模】例如：3fe（1 follower+2observer）+9be（fe与be独立部署）
【机器信息】CPU虚拟核/内存/网卡，例如：32C/128G/万兆
【联系方式】为了在解决问题过程中能及时联系到您获取一些日志信息，请补充下您的联系方式，例如：社区群12-金谡-jinsu@moojing.com，谢谢
【附件】
- fe.log/beINFO/相应截图
- 慢查询：
- Profile信息
- 并行度：show variables like ‘%parallel_fragment_exec_instance_num%’;
- pipeline是否开启：show variables like ‘%pipeline%’;
- be节点cpu和内存使用率截图
- 查询报错：
- query_dump，怎么获取query_dump文件
- be crash
- be.out
start time: Mon 12 Jun 2023 06:09:42 PM CST
query_id:f7768306-098a-11ee-a1df-5254005f1696, fragment_instance:f7768306-098a-11ee-a1df-5254005f16bd
*** Aborted at 1686620372 (unix time) try “date -d @1686620372” if you are using GNU date ***
PC: @ 0x3a37670 starrocks::vectorized::RuntimeBloomFilter<>::insert()
*** SIGSEGV (@0x7f3d7d000000) received by PID 1575299 (TID 0x7f76832c7700) from PID 2097152000; stack trace: ***
@ 0x481e332 google::(anonymous namespace)::FailureSignalHandler()
@ 0x7f774ab6d3ab os::Linux::chained_handler()
@ 0x7f774ab71efc JVM_handle_linux_signal
@ 0x7f774ab64d48 signalHandler()
@ 0x7f774a238420 (unknown)
@ 0x3a37670 starrocks::vectorized::RuntimeBloomFilter<>::insert()
@ 0x3a2aa88 starrocks::vectorized::RuntimeFilterHelper::fill_runtime_bloom_filter()
@ 0x2ec6b7a starrocks::pipeline::PartialRuntimeFilterMerger::merge_local_bloom_filters()
@ 0x2ec328e starrocks::pipeline::HashJoinBuildOperator::set_finishing()
@ 0x2e76ff7 starrocks::pipeline::PipelineDriver::_mark_operator_finishing()
@ 0x2e7802b starrocks::pipeline::PipelineDriver::process()
@ 0x2e6e5a3 starrocks::pipeline::GlobalDriverExecutor::_worker_thread()
@ 0x2680a05 starrocks::ThreadPool::dispatch_thread()
@ 0x267bf2a starrocks:
:supervise_thread()
@ 0x7f774a22c609 start_thread
@ 0x7f7749ff2133 clone
@ 0x0 (unknown)
- be.out
