[
https://issues.apache.org/jira/browse/HADOOP-11167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14161948#comment-14161948
]
Hadoop QA commented on HADOOP-11167:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12673280/HADOOP-11167.patch
against trunk revision 0fb2735.
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 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:green}+1 core tests{color}. The patch passed unit tests in
hadoop-common-project/hadoop-common.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4873//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/4873//console
This message is automatically generated.
> 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)
