You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@impala.apache.org by Dong Bo 董博 <do...@fosun.com> on 2018/01/30 08:59:24 UTC
Can not start impala Catalog and Daemons due to JVM FATAL
I am trying to merge Impala with a kerberized Hadoop platform , and failed to start catalogd and daemons.
Error message is not specific , all related files attached .
Impala Version : 2.11.0+cdh5.14.0+0-1.cdh5.14.0.p0.50.el7
JDK : jdk1.8.0_91
Error Content :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f23019d1c1f, pid=10116, tid=139788732049792
#
# JRE version: (8.0_91-b14) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 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
#
# An error report file with more information is saved as:
# /home/impala/hs_err_pid10116.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Thanks in Advance
Carl Dong
答复: 答复: Can not start impala Catalog and Daemons due to JVM FATAL
Posted by Dong Bo 董博 <do...@fosun.com>.
Yes , current kernel is kernel-3.10.0-514.21.2.el7.x86_64.
Solved by upgrade kernel to a higher version
Thanks
Carl
发件人: Jeszy [mailto:jeszyb@gmail.com]
发送时间: 2018年1月30日 19:17
收件人: user@impala.apache.org
主题: Re: 答复: Can not start impala Catalog and Daemons due to JVM FATAL
This is most likely caused by a RedHat bug - see this article:
https://access.redhat.com/solutions/3091371
On 30 January 2018 at 12:11, Dong Bo 董博 <do...@fosun.com>> wrote:
The strange thing is I can start statestore on the same server .
发件人: Dong Bo 董博
发送时间: 2018年1月30日 19:07
收件人: user@impala.apache.org<ma...@impala.apache.org>
主题: 答复: Can not start impala Catalog and Daemons due to JVM FATAL
Not found these 2 options in /etc/default/impala nor /etc/impala/conf , anywhere should I check ?
Btw , I am not using Cloudera Manager. Impala is installed with yum from cloudera repo.
发件人: Fawze Abujaber [mailto:fawzeaj@gmail.com]
发送时间: 2018年1月30日 17:31
收件人: user@impala.apache.org<ma...@impala.apache.org>
主题: Re: Can not start impala Catalog and Daemons due to JVM FATAL
Go to impala configuration and make the following parameters empty.
Catalog Server Core Dump Directory
Catalog Server Breakpad Dump Directory
On Tue, Jan 30, 2018 at 10:59 AM, Dong Bo 董博 <do...@fosun.com>> wrote:
I am trying to merge Impala with a kerberized Hadoop platform , and failed to start catalogd and daemons.
Error message is not specific , all related files attached .
Impala Version : 2.11.0+cdh5.14.0+0-1.cdh5.14.0.p0.50.el7
JDK : jdk1.8.0_91
Error Content :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f23019d1c1f, pid=10116, tid=139788732049792
#
# JRE version: (8.0_91-b14) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 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
#
# An error report file with more information is saved as:
# /home/impala/hs_err_pid10116.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Thanks in Advance
Carl Dong
Re: 答复: Can not start impala Catalog and Daemons due to JVM FATAL
Posted by Jeszy <je...@gmail.com>.
This is most likely caused by a RedHat bug - see this article:
https://access.redhat.com/solutions/3091371
On 30 January 2018 at 12:11, Dong Bo 董博 <do...@fosun.com> wrote:
> The strange thing is I can start statestore on the same server .
>
>
>
> *发件人:* Dong Bo 董博
> *发送时间:* 2018年1月30日 19:07
> *收件人:* user@impala.apache.org
> *主题:* 答复: Can not start impala Catalog and Daemons due to JVM FATAL
>
>
>
> Not found these 2 options in /etc/default/impala nor /etc/impala/conf ,
> anywhere should I check ?
>
> Btw , I am not using Cloudera Manager. Impala is installed with yum from
> cloudera repo.
>
>
>
> *发件人:* Fawze Abujaber [mailto:fawzeaj@gmail.com <fa...@gmail.com>]
> *发送时间:* 2018年1月30日 17:31
> *收件人:* user@impala.apache.org
> *主题:* Re: Can not start impala Catalog and Daemons due to JVM FATAL
>
>
>
> *Go to impala configuration and make the following parameters empty.*
>
>
>
> *Catalog Server Core Dump Directory*
>
>
>
> *Catalog Server Breakpad Dump Directory*
>
>
>
>
>
> On Tue, Jan 30, 2018 at 10:59 AM, Dong Bo 董博 <do...@fosun.com> wrote:
>
> I am trying to merge Impala with a kerberized Hadoop platform , and failed
> to start catalogd and daemons.
>
>
>
> Error message is not specific , all related files attached .
>
>
>
> Impala Version : 2.11.0+cdh5.14.0+0-1.cdh5.14.0.p0.50.el7
>
> JDK : jdk1.8.0_91
>
>
>
> Error Content :
>
>
>
> #
>
> # A fatal error has been detected by the Java Runtime Environment:
>
> #
>
> # SIGBUS (0x7) at pc=0x00007f23019d1c1f, pid=10116, tid=139788732049792
>
> #
>
> # JRE version: (8.0_91-b14) (build )
>
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 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
>
> #
>
> # An error report file with more information is saved as:
>
> # /home/impala/hs_err_pid10116.log
>
> #
>
> # If you would like to submit a bug report, please visit:
>
> # http://bugreport.java.com/bugreport/crash.jsp
>
> #
>
>
>
>
>
> Thanks in Advance
>
>
>
> Carl Dong
>
>
>
答复: Can not start impala Catalog and Daemons due to JVM FATAL
Posted by Dong Bo 董博 <do...@fosun.com>.
The strange thing is I can start statestore on the same server .
发件人: Dong Bo 董博
发送时间: 2018年1月30日 19:07
收件人: user@impala.apache.org
主题: 答复: Can not start impala Catalog and Daemons due to JVM FATAL
Not found these 2 options in /etc/default/impala nor /etc/impala/conf , anywhere should I check ?
Btw , I am not using Cloudera Manager. Impala is installed with yum from cloudera repo.
发件人: Fawze Abujaber [mailto:fawzeaj@gmail.com]
发送时间: 2018年1月30日 17:31
收件人: user@impala.apache.org<ma...@impala.apache.org>
主题: Re: Can not start impala Catalog and Daemons due to JVM FATAL
Go to impala configuration and make the following parameters empty.
Catalog Server Core Dump Directory
Catalog Server Breakpad Dump Directory
On Tue, Jan 30, 2018 at 10:59 AM, Dong Bo 董博 <do...@fosun.com>> wrote:
I am trying to merge Impala with a kerberized Hadoop platform , and failed to start catalogd and daemons.
Error message is not specific , all related files attached .
Impala Version : 2.11.0+cdh5.14.0+0-1.cdh5.14.0.p0.50.el7
JDK : jdk1.8.0_91
Error Content :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f23019d1c1f, pid=10116, tid=139788732049792
#
# JRE version: (8.0_91-b14) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 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
#
# An error report file with more information is saved as:
# /home/impala/hs_err_pid10116.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Thanks in Advance
Carl Dong
答复: Can not start impala Catalog and Daemons due to JVM FATAL
Posted by Dong Bo 董博 <do...@fosun.com>.
Not found these 2 options in /etc/default/impala nor /etc/impala/conf , anywhere should I check ?
Btw , I am not using Cloudera Manager. Impala is installed with yum from cloudera repo.
发件人: Fawze Abujaber [mailto:fawzeaj@gmail.com]
发送时间: 2018年1月30日 17:31
收件人: user@impala.apache.org
主题: Re: Can not start impala Catalog and Daemons due to JVM FATAL
Go to impala configuration and make the following parameters empty.
Catalog Server Core Dump Directory
Catalog Server Breakpad Dump Directory
On Tue, Jan 30, 2018 at 10:59 AM, Dong Bo 董博 <do...@fosun.com>> wrote:
I am trying to merge Impala with a kerberized Hadoop platform , and failed to start catalogd and daemons.
Error message is not specific , all related files attached .
Impala Version : 2.11.0+cdh5.14.0+0-1.cdh5.14.0.p0.50.el7
JDK : jdk1.8.0_91
Error Content :
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGBUS (0x7) at pc=0x00007f23019d1c1f, pid=10116, tid=139788732049792
#
# JRE version: (8.0_91-b14) (build )
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 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
#
# An error report file with more information is saved as:
# /home/impala/hs_err_pid10116.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
Thanks in Advance
Carl Dong
Re: Can not start impala Catalog and Daemons due to JVM FATAL
Posted by Fawze Abujaber <fa...@gmail.com>.
Go to impala configuration and make the following parameters empty.
Catalog Server Core Dump Directory
Catalog Server Breakpad Dump Directory
On Tue, Jan 30, 2018 at 10:59 AM, Dong Bo 董博 <do...@fosun.com> wrote:
> I am trying to merge Impala with a kerberized Hadoop platform , and failed
> to start catalogd and daemons.
>
>
>
> Error message is not specific , all related files attached .
>
>
>
> Impala Version : 2.11.0+cdh5.14.0+0-1.cdh5.14.0.p0.50.el7
>
> JDK : jdk1.8.0_91
>
>
>
> Error Content :
>
>
>
> #
>
> # A fatal error has been detected by the Java Runtime Environment:
>
> #
>
> # SIGBUS (0x7) at pc=0x00007f23019d1c1f, pid=10116, tid=139788732049792
>
> #
>
> # JRE version: (8.0_91-b14) (build )
>
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 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
>
> #
>
> # An error report file with more information is saved as:
>
> # /home/impala/hs_err_pid10116.log
>
> #
>
> # If you would like to submit a bug report, please visit:
>
> # http://bugreport.java.com/bugreport/crash.jsp
>
> #
>
>
>
>
>
> Thanks in Advance
>
>
>
> Carl Dong
>