[
https://issues.apache.org/jira/browse/AMBARI-9832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340336#comment-14340336
]
Hadoop QA commented on AMBARI-9832:
-----------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12701379/AMBARI-9832_branch_2.0.0.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1841//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1841//console
This message is automatically generated.
> JournalNode kerberos configs are missing when trying to enable HA
> -----------------------------------------------------------------
>
> Key: AMBARI-9832
> URL: https://issues.apache.org/jira/browse/AMBARI-9832
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Andrii Babiichuk
> Assignee: Andrii Babiichuk
> Priority: Critical
> Fix For: 2.0.0
>
> Attachments: AMBARI-9832.patch, AMBARI-9832_branch_2.0.0.patch
>
>
> 1. build a two node cluster, with 1 ZK (everything on c6401). c6402 should
> only have DN, NM and clients
> 2. Then add a host c6403 with just DN, NM and clients
> 3. Then add two ZKs (to c6402 and c6403)
> 4. Then enable kerb.
> 5. Then try to enable namenode HA.
> Result:
> JournalNodes start fails.
> During enabling HA journalnode "kerberos configs" were added to hdfs-site.xml:
> {noformat}
> [root@c6401 data]# grep -ri
> "dfs.journalnode.kerberos.internal.spnego.principal" *
> command-175.json:
> "dfs.journalnode.kerberos.internal.spnego.principal":
> "HTTP/[email protected]",
> command-179.json:
> "dfs.journalnode.kerberos.internal.spnego.principal":
> "HTTP/[email protected]",
> command-184.json:
> "dfs.journalnode.kerberos.internal.spnego.principal":
> "HTTP/[email protected]",
> {noformat}
> But when JNs were stating those configurations have not been in hdfs-site.xml
> and command.json.
> {noformat}
> [root@c6401 data]# grep -ri
> "dfs.journalnode.kerberos.internal.spnego.principal" command-188.json
> [root@c6401 data]#
> {noformat}
> {code}
> Exception in thread "main" java.io.IOException: Running in secure mode, but
> config doesn't have a keytab
> at
> org.apache.hadoop.security.SecurityUtil.login(SecurityUtil.java:236)
> at
> org.apache.hadoop.hdfs.qjournal.server.JournalNode.start(JournalNode.java:144)
> {code}
> *I could not reproduce it at the second attempt*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
