hadoop-hdfs-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HDFS-4982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Todd Lipcon updated HDFS-4982:
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.0-beta
                   3.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

committed to branch-2, branch-2.1, trunk
                
> 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