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/11/05 13:48:34 UTC
[jira] [Commented] (HADOOP-11272) Allow ZKSignerSecretProvider and
ZKDelegationTokenSecretManager to use the same curator client
[ https://issues.apache.org/jira/browse/HADOOP-11272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198331#comment-14198331 ]
Hadoop QA commented on HADOOP-11272:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12679517/HADOOP-11272.1.patch
against trunk revision 8e9502e.
{color:green}+1 @author{color}. The patch does not contain any @author tags.
{color:green}+1 tests included{color}. The patch appears to include 2 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.ssl.TestReloadingX509TrustManager
org.apache.hadoop.ha.TestZKFailoverControllerStress
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5030//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5030//console
This message is automatically generated.
> Allow ZKSignerSecretProvider and ZKDelegationTokenSecretManager to use the same curator client
> ----------------------------------------------------------------------------------------------
>
> Key: HADOOP-11272
> URL: https://issues.apache.org/jira/browse/HADOOP-11272
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Arun Suresh
> Assignee: Arun Suresh
> Attachments: HADOOP-11272.1.patch
>
>
> Currently the {{AuthenticationFilter}} cannot be configured to use {{ZKDelegationTokenSecretManager}} and {{ZKSignerSecretProvider}} together if the Zookeeper is a kerberized cluster.
> The zookeeper client requires certain configuration parameters to be set as SystemProperties (The issue has also been reported [here|https://issues.apache.org/jira/browse/YARN-913?focusedCommentId=14142086&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14142086]). Thus if a single process needs to use both {{ZKDelegationTokenSecretManager}} and {{ZKSignerSecretProvider}} then it should use the same client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)