hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4982) JournalNode should relogin from keytab before fetching logs from other JNs
Date Fri, 12 Jul 2013 20:55:48 GMT

    [ https://issues.apache.org/jira/browse/HDFS-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13707359#comment-13707359
] 

Hudson commented on HDFS-4982:
------------------------------

SUCCESS: Integrated in Hadoop-trunk-Commit #4077 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/4077/])
HDFS-4982. JournalNode should relogin from keytab before fetching logs from other JNs. Contributed
by Todd Lipcon. (todd: http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1502682)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/qjournal/server/Journal.java

                
> JournalNode should relogin from keytab before fetching logs from other JNs
> --------------------------------------------------------------------------
>
>                 Key: HDFS-4982
>                 URL: https://issues.apache.org/jira/browse/HDFS-4982
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: journal-node, security
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: 3.0.0, 2.1.0-beta
>
>         Attachments: hdfs-4982.txt
>
>
> We've seen an issue in a secure cluster where, after a failover, the new NN isn't able
to properly coordinate QJM recovery. The JNs fail to fetch logs from each other due to apparently
not having a Kerberos TGT. It seems that we need to add the {{checkTGTAndReloginFromKeytab}}
call prior to making the HTTP connection, since the java HTTP stuff doesn't do an automatic
relogin

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message