Details
-
Bug
-
Status: Open
-
Blocker
-
Resolution: Unresolved
-
Impala 4.4.0
-
None
-
None
-
ghx-label-12
Description
Dataload crashes in ASAN builds with the following error and stack reported in the coordinator's impalad.ERROR log file:
F0227 14:03:39.248898 57142 impala-server.cc:1179] Check failed: query_log_est_total_size_ >= 0 (-4702111234474152144 vs. 0) *** Check failure stack trace: *** @ 0x63ed896 google::DumpStackTraceAndExit() @ 0x63e4abd google::LogMessage::Fail() @ 0x63e69f4 google::LogMessage::SendToLog() @ 0x63e449c google::LogMessage::Flush() @ 0x63e6f19 google::LogMessageFatal::~LogMessageFatal() @ 0x3169806 impala::ImpalaServer::ArchiveQuery() @ 0x3172b88 impala::ImpalaServer::CloseClientRequestState() @ 0x3159b58 impala::ImpalaServer::FinishUnregisterQuery() @ 0x31a7129 boost::_bi::bind_t<>::operator()<>() @ 0x31a6b47 boost::detail::function::void_function_obj_invoker2<>::invoke() @ 0x31ab444 boost::function2<>::operator()() @ 0x31a9834 impala::ThreadPool<>::WorkerThread() @ 0x31aa53c boost::_bi::bind_t<>::operator()() @ 0x2b97477 boost::function0<>::operator()() @ 0x37a1e60 impala::Thread::SuperviseThread() @ 0x37ae169 boost::_bi::list5<>::operator()<>() @ 0x37adfbc boost::_bi::bind_t<>::operator()() @ 0x4effb37 thread_proxy @ 0x7f0296853609 start_thread @ 0x7f029486d133 clone Minidump in thread [57142]unregistration-worker(2:4) running query 0000000000000000:0000000000000000, fragment instance 0000000000000000:0000000000000000 Wrote minidump to /home/ubuntu/Impala/logs/data_loading/minidumps/impalad/f744d884-2ca0-4e2c-57e62abc-35462a60.dmp
The crash seems to happen during loading the TPC-DS data set.
First seen in a downstream build; it can also be reproduced in the upstream build environment, see
https://jenkins.impala.io/view/Ubuntu%2020/job/ubuntu-20.04-from-scratch/1830/