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 "Hadoop QA (JIRA)" <ji...@apache.org> on 2014/09/29 17:45:34 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14151816#comment-14151816 ] 

Hadoop QA commented on HADOOP-11113:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12671793/HADOOP-11113.1.patch
  against trunk revision cf4631d.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 4 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 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version 2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:red}-1 core tests{color}.  The patch failed these unit tests in hadoop-common-project/hadoop-auth hadoop-common-project/hadoop-common hadoop-common-project/hadoop-kms:

                  org.apache.hadoop.security.token.delegation.web.TestWebDelegationToken
                  org.apache.hadoop.metrics2.impl.TestMetricsSystemImpl

    {color:green}+1 contrib tests{color}.  The patch passed contrib unit tests.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/4825//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/4825//console

This message is automatically generated.

> 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
>         Attachments: HADOOP-11113.1.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)