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 "Arun Suresh (JIRA)" <ji...@apache.org> on 2014/10/07 15:32:34 UTC

[jira] [Commented] (HADOOP-11167) ZKDelegationTokenSecretManager doesn't always handle zk node existing correctly

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

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

+1 Looks straight forward... Thanks for the test cases [~gchanan]

> 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.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)