gaodayue opened a new issue #3591:
URL: https://github.com/apache/incubator-doris/issues/3591
**Describe the bug**
Aggregate query leads to BE coredump with the following logs and stack.
```
I0514 13:00:50.688493 25754 plan_fragment_executor.cpp:272] Open():
fragment_instance_id=55e2b2da7c1b4cf5-951b9bb6ac07cfa8
F0514 13:00:50.688647 25754 reservation_tracker.cc:286] Check failed:
tracker->mem_tracker_ == nullptr || !tracker->mem_tracker_->has_limit()
*** Check failure stack trace: ***
@ 0x3005c2d google::LogMessage::Fail()
@ 0x3007ab4 google::LogMessage::SendToLog()
@ 0x3005754 google::LogMessage::Flush()
@ 0x30084e9 google::LogMessageFatal::~LogMessageFatal()
@ 0x1be6450 doris::ReservationTracker::TransferReservationTo()
@ 0x1bdfb37
doris::BufferPool::ClientHandle::TransferReservationFrom()
@ 0x1beacc1 doris::InitialReservations::Claim()
@ 0x206bb1c doris::ExecNode::claim_buffer_reservation()
@ 0x2172b8b doris::NewPartitionedAggregationNode::open()
@ 0x1c16427 doris::PlanFragmentExecutor::open_internal()
@ 0x1c1624a doris::PlanFragmentExecutor::open()
@ 0x1b6a12d doris::FragmentExecState::execute()
@ 0x1b6bb05 doris::FragmentMgr::exec_actual()
@ 0x1b7d2ce boost::_mfi::mf2<>::operator()()
@ 0x1b7c45d boost::_bi::list3<>::operator()<>()
@ 0x1b7b1b3 boost::_bi::bind_t<>::operator()()
@ 0x1b79a67
boost::detail::function::void_function_obj_invoker0<>::invoke()
@ 0x19d97f6 boost::function0<>::operator()()
@ 0x19d8a12 doris::ThreadPool::work_thread()
@ 0x19e0fa0 boost::_mfi::mf1<>::operator()()
@ 0x19e0ef8 boost::_bi::list2<>::operator()<>()
@ 0x19e0dd3 boost::_bi::bind_t<>::operator()()
@ 0x19e0cba boost::detail::thread_data<>::run()
@ 0x271db0d thread_proxy
```
The root cause is that #3383 sets limit to instance mem tracker, which is
not expected by ReservationTracker.
**Additional context**
Version: master branch
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
