Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

HDP 2.6.1 enable Kerberos in Ambari - datanodes core dump

avatar
New Member

I installed a fresh HDP 2.6.1 cluster and then used Ambari to enable Kerberos. When it gets to the point of Start and Test services it hangs for a long time on starting the Namenode. Reviewing logs on the namenodes doesn't reveal much but all of the datanodes have jsvc.out files showing that the jsvc is continually core dumping. The datanode.out log file doesn't contain anything useful because it never gets up and running.

1 ACCEPTED SOLUTION

avatar
Master Mentor

@Aaron Norton

Are you using RedHat Enterprise Linux?

Can you please check if the "hs_err_pid.log" file is generated for your DataNode, this file is created when the JVM crashes.

As it is jsvc crash (and if you have recently upgraded your redhat kernel) then it might be related to: https://issues.apache.org/jira/browse/HDFS-12029

https://issues.apache.org/jira/browse/DAEMON-363

If this is the case then increasing the StackSize (to something higher like -Xss2048k) Of your DataNode might help DataNode to comeup fine.

.

View solution in original post

2 REPLIES 2

avatar
Master Mentor

@Aaron Norton

Are you using RedHat Enterprise Linux?

Can you please check if the "hs_err_pid.log" file is generated for your DataNode, this file is created when the JVM crashes.

As it is jsvc crash (and if you have recently upgraded your redhat kernel) then it might be related to: https://issues.apache.org/jira/browse/HDFS-12029

https://issues.apache.org/jira/browse/DAEMON-363

If this is the case then increasing the StackSize (to something higher like -Xss2048k) Of your DataNode might help DataNode to comeup fine.

.

avatar
Contributor

@Aaron Norton

As per @Jay SenSharma comment, this is the Red Hat KB article probably related to your issue: https://access.redhat.com/solutions/3091371