You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2014/10/01 01:49:34 UTC

[jira] [Updated] (HADOOP-11113) Namenode not able to reconnect to KMS after KMS restart

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

Andrew Wang updated HADOOP-11113:
---------------------------------
       Resolution: Fixed
    Fix Version/s: 2.6.0
           Status: Resolved  (was: Patch Available)

Committed to trunk, branch-2, branch-2.6, thanks for working on this Arun.

> Namenode not able to reconnect to KMS after KMS restart
> -------------------------------------------------------
>
>                 Key: HADOOP-11113
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11113
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Arun Suresh
>            Assignee: Arun Suresh
>             Fix For: 2.6.0
>
>         Attachments: HADOOP-11113.1.patch, HADOOP-11113.2.patch, HADOOP-11113.3.patch
>
>
> It is observed that if KMS is restarted without the Namenode being restarted, NN will not be able to reconnect with KMS.
> It seems that the KMS auth cookie goes stale and it does not get flushed, so the KMSClient in the NN cannot reconnect with the new KMS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)