hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11272) Allow ZKSignerSecretProvider and ZKDelegationTokenSecretManager to use the same curator client
Date Thu, 06 Nov 2014 01:46:34 GMT

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

Aaron T. Myers commented on HADOOP-11272:
-----------------------------------------

+1, the latest patch looks good to me. I'm confident that the test failures are unrelated
as well - both tend to flake out when run on slower/overloaded machines.

I'm going to commit this momentarily.

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

Mime
View raw message