[jira] [Created] (IMPALA-6414) Imapalad binary failed to start with SIGSEGV with GPerfTools 2.6.3 on certain platforms

["Michael Ho (JIRA)" <ji...@apache.org>]

Michael Ho created IMPALA-6414:
----------------------------------

             Summary: Imapalad binary failed to start with SIGSEGV with GPerfTools 2.6.3 on certain platforms
                 Key: IMPALA-6414
                 URL: https://issues.apache.org/jira/browse/IMPALA-6414
             Project: IMPALA
          Issue Type: Bug
          Components: Backend
    Affects Versions: Impala 2.12.0
            Reporter: Michael Ho
            Assignee: Michael Ho


A recent [commit|https://github.com/apache/impala/commit/df3a440fff38225a03879955c99a87d8ced3b13a] upgraded GPerfTools to version 2.6.3. Apparently, this mysteriously caused Impala to fail to start on certain platforms (e.g. Oracle Enterprise Linux 6.9). There is no core file or anything found when this failed.
{noformat}
$ /opt/cloudera/parcels/CDH-5.15.0-1.cdh5.15.0.p0.176/lib/impala/sbin-retail/impalad
Segmentation fault
$ strace /opt/cloudera/parcels/CDH-5.15.0-1.cdh5.15.0.p0.176/lib/impala/sbin-retail/impalad
execve("/opt/cloudera/parcels/CDH-5.15.0-1.cdh5.15.0.p0.176/lib/impala/sbin-retail/impalad", ["/opt/cloudera/parcels/CDH-5.15.0"...], [/* 23 vars */]) = -1 EINVAL (Invalid argument)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SI_KERNEL, si_addr=0} ---
+++ killed by SIGSEGV +++
Segmentation fault
{noformat}
It was verified that downgrading GPerfTools to previous version (2.5) made the problem go away.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)