[Bug] be crash problem sometimes #7853
Description
Search before asking
- I had searched in the issues and found no similar issues.
Version
0.12.21
What's Wrong?
Occasionally, a be node directly hangs up. Check the monitoring to see that the machine load is relatively high (mainly due to high disk IO write) .
this be.out log :
*** Aborted at 1642887639 (unix time) try "date -d @1642887639" if you are using GNU date ***
PC: @ 0x107e35f doris_udf::FunctionContext::free()
*** SIGSEGV (@0x0) received by PID 234710 (TID 0x7fe2ca174700) from PID 0; stack trace: ***
@ 0x7fe310ec52f0 (unknown)
@ 0x107e35f doris_udf::FunctionContext::free()
@ 0xdbdd95 doris::CaseExpr::close()
@ 0xd381e3 doris::ExprContext::close()
@ 0xd2faf0 doris::Expr::close()
@ 0x147ef0a doris::stream_load::OlapTableSink::close()
@ 0x10221de doris::PlanFragmentExecutor::close()
@ 0xfb3ffd doris::FragmentExecState::execute()
@ 0xfb5aa6 doris::FragmentMgr::exec_actual()
@ 0xfbc774 boost::detail::function::void_function_obj_invoker0<>::invoke()
@ 0xf87f95 doris::PriorityThreadPool::work_thread()
@ 0x1a3e25d thread_proxy
@ 0x7fe310c7ae25 start_thread
@ 0x7fe310f8dbad __clone
What You Expected?
normal
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct