[IMPALA-3621] impala core down with minidump

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: Impala 2.5.0
• Component/s: Backend
• Environment: impala commit is https://github.com/cloudera/Impala/commit/f6289da9d8dd4a4f74cc6566425b16a5c1695bb8
• Assignee: Unassigned
• Reporter: fishing
• Created: 26/May/16 03:12
• Updated: 26/May/17 17:55
• Resolved: 19/Jan/17 21:40

Description

dumps :

first:
(gdb) bt
#0 impala::MemTracker::CheckLimitExceeded (this=0x0) at /export/ldb/Impala-cdh5.7-fbthrift/be/src/runtime/mem-tracker.h:352
#1 impala::MemTracker::LimitExceeded (this=0x0) at /export/ldb/Impala-cdh5.7-fbthrift/be/src/runtime/mem-tracker.h:266
#2 impala::FragmentMgr::ExecPlanFragment (this=0xc8cdae0, exec_params=...) at /export/ldb/Impala-cdh5.7-fbthrift/be/src/service/fragment-mgr.cc:52
#3 0x0000000000cc9ef8 in impala::ImpalaInternalService::ExecPlanFragment (this=<optimized out>, return_val=..., params=...) at /export/ldb/Impala-cdh5.7-fbthrift/be/src/service/impala-internal-service.h:37
#4 0x0000000000eeb737 in impala::ImpalaInternalServiceProcessor::process_ExecPlanFragment (this=0xc8b24d0, seqid=1, iprot=<optimized out>, oprot=0xd06da80, connectionContext=<optimized out>) at /export/ldb/Imp
ala-cdh5.7-fbthrift/be/generated-sources/gen-cpp/ImpalaInternalService.cpp:1709
#5 0x0000000000ee7b66 in impala::ImpalaInternalServiceProcessor::dispatchCall (this=0xc8b24d0, iprot=0xd06dac0, oprot=0xd06da80, fname=..., seqid=1, connectionContext=0xd1edd30) at /export/ldb/Impala-cdh5.7-fb
thrift/be/generated-sources/gen-cpp/ImpalaInternalService.cpp:1679
#6 0x000000000086df6c in apache::thrift::TDispatchProcessor::process (this=0xc8b24d0, in=..., out=..., connectionContext=0xd1edd30) at /export/ldb/Impala-cdh5.7-fbthrift/thirdparty/fbthrift-0.32.0/build/includ
e/thrift/lib/cpp/TDispatchProcessor.h:124
#7 0x00007f826e3efdf5 in ?? ()
#8 0x000000000d1edd30 in ?? ()
#9 0x000000000d1edce0 in ?? ()
#10 0x0000000000000000 in ?? ()

second:
(gdb) bt
#0 0x00007f88279c79d5 in ?? ()
#1 0x00007f84884cc4d0 in ?? ()
#2 0x00007f84884cc5e0 in ?? ()
#3 0x000000000945ba00 in ?? ()
#4 0x00007f84884cc56e in ?? ()
#5 0x00000000ac505f38 in ?? ()
#6 0x000000009935ef28 in ?? ()
#7 0x00007f84884cc750 in ?? ()
#8 0x000000009935ed80 in ?? ()
#9 0x00007f84884cc8f0 in ?? ()
#10 0x0000000000ea6d39 in impala::PartitionedHashJoinNode::ProcessBuildInput (this=0x9935efd8, state=<error reading variable: Cannot access memory at address 0xde34c780>, level=<error reading variable: Cannot a
ccess memory at address 0xde34c778>) at /export/ldb/Impala-cdh5.7-fbthrift/be/src/exec/partitioned-hash-join-node.cc:700
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

third:

Issue Links

• duplicates: IMPALA-5377 IMPALAD Crashed With the impala starting large number of JDBC accessing