since i see you logs says that you are downlading the parcels from /opt/cloudera/parcels/CDH-5.11.1-1.cdh5.11.1.p0.4/lib/impala/../..
it says ( in your log file ) go to
/var/log/impalad/impalad.ERROR
it may direct to mini-dump logs (/var/log/impala-minidumps/impalad / )
if you open the file and if you come across the JRE runtime error plus if it complains about the core dump .
Then it is the bug that is related to Linux kernel , impala's JRE error .
the fix is to increase the Stack thread . do the below steps
the error should look like this
A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007fa6b9f80c18, pid=3819, tid=0x00007fa6cfdb4900
#
# JRE version: (8.0_131-b11) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.131-b11 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# j java.lang.Object.<clinit>()V+0
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
The fix is
In Cloduera manager UI -> Cluster -> Go to Impala - Configuration tab .
Search
Step 1 :
Impala Daemon properties:
Impala Daemon Environment Advanced Configuration Snippet (Safety Valve)
apply the JAVA_TOOL_OPTIONS=-Xss2m
Steo 2 :
Apply the same for Impala Catalog -
"Impala Catalog Server Environment Advanced Configuration Snippet (Safety Valve)"
before you restart the catalog daemon.
JAVA_TOOL_OPTIONS=-Xss2m
Reason - The crash was caused by a change to the linux kernel that modified the memory layout around JAVAthread stacks.
JIRA - - https://issues.apache.org/jira/browse/DAEMON-363
Please let me know if that works
