yiguolei opened a new pull request, #17212:
URL: https://github.com/apache/doris/pull/17212
# Proposed changes
0# doris::signal::(anonymous namespace)::FailureSignalHandler(int,
siginfo_t*, void*) at /root/doris/be/src/common/signal_handler.h:420
1# os::Linux::chained_handler(int, siginfo*, void*) in
/usr/local/jdk1.8.0_301/jre/lib/amd64/server/libjvm.so
2# JVM_handle_linux_signal in
/usr/local/jdk1.8.0_301/jre/lib/amd64/server/libjvm.so
3# signalHandler(int, siginfo*, void*) in
/usr/local/jdk1.8.0_301/jre/lib/amd64/server/libjvm.so
4# 0x00007F6498457400 in /lib64/libc.so.6
5# je_large_prof_tctx_get at ../src/large.c:374
6# je_free_default at ../src/jemalloc.c:2790
7# __GI__dl_deallocate_tls in /lib64/ld-linux-x86-64.so.2
8# __free_stacks in /lib64/libpthread.so.0
9# __deallocate_stack in /lib64/libpthread.so.0
10# pthread_join in /lib64/libpthread.so.0
11# std::thread::join() in /opt/doris/doris/be/lib/doris_be
12# doris::PlanFragmentExecutor::open_vectorized_internal() at
/root/doris/be/src/runtime/plan_fragment_executor.cpp:338
13# doris::PlanFragmentExecutor::open() at
/root/doris/be/src/runtime/plan_fragment_executor.cpp:253
14# doris::FragmentExecState::execute() at
/root/doris/be/src/runtime/fragment_mgr.cpp:251
15#
doris::FragmentMgr::_exec_actual(std::shared_ptr<doris::FragmentExecState>,
std::function<void (doris::PlanFragmentExecutor*)>) at
/root/doris/be/src/runtime/fragment_mgr.cpp:498
16# std::_Function_handler<void (),
doris::FragmentMgr::exec_plan_fragment(doris::TExecPlanFragmentParams const&,
std::function<void
(doris::PlanFragmentExecutor*)>)::{lambda()#1}>::_M_invoke(std::_Any_data
const&) at /var/local/ldb-toolchain/include/c++/11/bits/std_function.h:291
17# doris::ThreadPool::dispatch_thread() at
/root/doris/be/src/util/threadpool.cpp:542
18# doris::Thread::supervise_thread(void*) at
/root/doris/be/src/util/thread.cpp:455
19# start_thread in /lib64/libpthread.so.0
## Problem summary
Doris will start report thread and join thread during fragment execution.
There are many problems if create and destroy thread very frequently. Jemalloc
may not behave very well, it may crashed.
https://github.com/jemalloc/jemalloc/pull/1405
It is better to using thread pool to do these tasks.
## Checklist(Required)
* [ ] Does it affect the original behavior
* [ ] Has unit tests been added
* [ ] Has document been added or modified
* [ ] Does it need to update dependencies
* [ ] Is this PR support rollback (If NO, please explain WHY)
## Further comments
If this is a relatively large or complex change, kick off the discussion at
[[email protected]](mailto:[email protected]) by explaining why you
chose the solution you did and what alternatives you considered, etc...
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
