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] [Updated] (HADOOP-11272) Allow ZKSignerSecretProvider and ZKDelegationTokenSecretManager to use the same curator client
Date Wed, 05 Nov 2014 11:49:35 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-11272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Arun Suresh updated HADOOP-11272:
---------------------------------
    Target Version/s: 2.6.0
              Status: Patch Available  (was: Open)

> 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