hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun Suresh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11167) ZKDelegationTokenSecretManager doesn't always handle zk node existing correctly
Date Fri, 10 Oct 2014 16:55:34 GMT

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

Arun Suresh commented on HADOOP-11167:
--------------------------------------

One of the findBugs warning will be resolved by HADOOP-11122, the other is unrelated to the
patch
The release audit warning is unrelated to the patch

> ZKDelegationTokenSecretManager doesn't always handle zk node existing correctly
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-11167
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11167
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.0
>            Reporter: Gregory Chanan
>            Assignee: Gregory Chanan
>         Attachments: HADOOP-11167.2.patch, HADOOP-11167.patch, HADOOP-11167.patch
>
>
> The ZKDelegationTokenSecretManager is inconsistent in how it handles curator checkExists
calls.  Sometimes it assumes null response means the node exists, sometimes it doesn't.  This
causes it to be buggy in some cases.



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

Mime
View raw message