Member since
05-16-2016
783
Posts
112
Kudos Received
39
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1403 | 06-12-2019 09:27 AM | |
2426 | 05-27-2019 08:29 AM | |
4345 | 05-27-2018 08:49 AM | |
3779 | 05-05-2018 10:47 PM | |
2423 | 05-05-2018 07:32 AM |
06-30-2017
01:53 AM
You Welcome mate 🙂
... View more
06-29-2017
11:39 PM
Check your /etc/mysql/my.cnf see if you are commenting out the because it solved me . also check this attribute bind-address
... View more
06-29-2017
11:23 PM
1 Kudo
@Tim Armstrongon more question Could you let me know the Kernel version that it would fail (Centos / RHEL ) Since it is only being tested in testing enviroment , what should be done to the production box ?
... View more
06-29-2017
04:58 PM
sounds good . whats ur kernel / os version ?
... View more
06-29-2017
05:33 AM
12 Kudos
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
... View more
06-28-2017
10:05 PM
Would you mind deleting the Impala Catalog and Statestore instance . Add a new instance one more . see if those errors popping up. i hardly remeber I had this issue . the above fixed it for me .
... View more
06-28-2017
09:45 PM
@mbigelow I got confused . THanks for clarifying it .
... View more
06-28-2017
06:14 PM
Did you try bounchign the cluster back after those changes in hdfs , core site xml ? please let me know
... View more
06-28-2017
05:45 AM
1 Kudo
Would you consider using Bucketing instead of partitioning because it decomposes data sets into much more manageable parts but still depends on the use case. insertion may take some time but intended for fast read .
... View more