Hey Saeid, There isn't much we can do without knowing the actual query, logs or the profile but there have been some fixes lately related to Impala crashes in SerializeOrFinalize() function. E.g. these are the one I found with a quick Jira check: https://issues.apache.org/jira/browse/IMPALA-8969 https://issues.apache.org/jira/browse/IMPALA-9809
Cheers, Gabor On Wed, Jan 13, 2021 at 2:59 PM Saeid Sattari <saeid.satt...@gmail.com> wrote: > Hi All, > > We are using Impala 3.2.0 and sometimes most of the impala daemons crash > with the following error. Does anyone have an idea why this happens or can > be solved? Thank you in advance. > > Best, > > Wrote minidump to >> /var/log/impala-minidumps/impalad/5567dc2f-7d3f-4e0a-1f1c11b4-f6079dbb.dmp >> # >> # A fatal error has been detected by the Java Runtime Environment: >> # >> # SIGSEGV (0xb) at pc=0x00000000013203f8, pid=20451, >> tid=0x00007fa91ae74700 >> # >> # JRE version: Java(TM) SE Runtime Environment (8.0_181-b13) (build >> 1.8.0_181-b13) >> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.181-b13 mixed mode >> linux-amd64 ) >> # Problematic frame: >> # C [impalad+0xf203f8] >> impala::AggFnEvaluator::SerializeOrFinalize(impala::Tuple*, >> impala::SlotDescriptor const&, impala::Tuple*, void*)+0x48 >> # >> # Failed to write core dump. Core dumps have been disabled. To enable >> core dumping, try "ulimit -c unlimited" before starting Java again >> # >> # An error report file with more information is saved as: >> # /run/cloudera-scm-agent/process/43517-impala-IMPALAD/hs_err_pid20451.log >> # >> # If you would like to submit a bug report, please visit: >> # http://bugreport.java.com/bugreport/crash.jsp >> # The crash happened outside the Java Virtual Machine in native code. >> # See problematic frame for where to report the bug. > >
