Gabriel39 opened a new pull request, #52850:
URL: https://github.com/apache/doris/pull/52850

   …epare execution (#51492)
   
   Issue Number: close #51491
   
   Problem Summary:
   When the queue of the FragmentMgrAsync thread pool is full, newly submitted 
tasks are rejected and return early. However, previously submitted tasks may 
still be scheduled for execution later. This can lead to premature destruction 
of objects such as PipelineFragmentContext and TPipelineFragmentParams that are 
referenced by those tasks, resulting in null pointer exceptions during task 
execution and ultimately causing a coredump.
   
   The pr policy is to wait until all previously submitted tasks are completed 
before returning.
   
   ```
   *** SIGSEGV address not mapped to object (@0x1c8) received by PID 3941201 
(TID 2115617 OR 0xfe1685bb97f0) from PID 456; stack trace: ***
    0# doris::signal::(anonymous namespace)::FailureSignalHandler(int, 
siginfo_t*, void*) at 
/home/jenkins_agent/workspace/BigDataComponent_doris-unified-arm-release/be/src/common/signal_handler.h:421
    1# os::Linux::chained_handler(int, siginfo_t*, void*) in 
/usr/jdk64/current/jre/lib/aarch64/server/libjvm.so
    2# JVM_handle_linux_signal in 
/usr/jdk64/current/jre/lib/aarch64/server/libjvm.so
    3# signalHandler(int, siginfo_t*, void*) in 
/usr/jdk64/current/jre/lib/aarch64/server/libjvm.so
    4# 0x0000FFFF6B2A07C0 in linux-vdso.so.1
    5# doris::TUniqueId::TUniqueId(doris::TUniqueId const&) at 
/home/jenkins_agent/workspace/BigDataComponent_doris-unified-arm-release/gensrc/build/gen_cpp/Types_types.cpp:2354
    6# doris::AttachTask::AttachTask(doris::QueryContext*) at 
/home/jenkins_agent/workspace/BigDataComponent_doris-unified-arm-release/be/src/runtime/thread_context.cpp:60
    7# std::_Function_handler<void (), 
doris::pipeline::PipelineXFragmentContext::_build_pipeline_x_tasks(doris::TPipelineFragmentParams
 const&, doris::ThreadPool*)::$_0>::_M_invoke(std::_Any_data const&) at 
/usr/lib/gcc/aarch64-linux-gnu/13/../../../../include/c++/13/bits/std_function.h:290
    8# doris::ThreadPool::dispatch_thread() at 
/home/jenkins_agent/workspace/BigDataComponent_doris-unified-arm-release/be/src/util/threadpool.cpp:552
    9# doris::Thread::supervise_thread(void*) at 
/home/jenkins_agent/workspace/BigDataComponent_doris-unified-arm-release/be/src/util/thread.cpp:499
   10# 0x0000FFFF6AF187AC in /lib64/libpthread.so.0
   11# 0x0000FFFF6B16548C in /lib64/libc.so.6
   ```
   
   ### What problem does this PR solve?
   
   Issue Number: close #xxx
   
   Related PR: #xxx
   
   Problem Summary:
   
   ### Release note
   
   None
   
   ### Check List (For Author)
   
   - Test <!-- At least one of them must be included. -->
       - [ ] Regression test
       - [ ] Unit Test
       - [ ] Manual test (add detailed scripts or steps below)
       - [ ] No need to test or manual test. Explain why:
           - [ ] This is a refactor/code format and no logic has been changed.
           - [ ] Previous test can cover this change.
           - [ ] No code files have been changed.
           - [ ] Other reason <!-- Add your reason?  -->
   
   - Behavior changed:
       - [ ] No.
       - [ ] Yes. <!-- Explain the behavior change -->
   
   - Does this need documentation?
       - [ ] No.
       - [ ] Yes. <!-- Add document PR link here. eg: 
https://github.com/apache/doris-website/pull/1214 -->
   
   ### Check List (For Reviewer who merge this PR)
   
   - [ ] Confirm the release note
   - [ ] Confirm test cases
   - [ ] Confirm document
   - [ ] Add branch pick label <!-- Add branch pick label that this PR should 
merge into -->
   
   


-- 
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]

Reply via email to