hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Chanan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11973) Some ZkDelegationTokenSecretManager znodes do not have ACLs
Date Mon, 18 May 2015 21:35:00 GMT

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

Gregory Chanan commented on HADOOP-11973:

looks like the underlying issue is CURATOR-221, I'm investigating if there is a workaround
we can use.

> Some ZkDelegationTokenSecretManager znodes do not have ACLs
> -----------------------------------------------------------
>                 Key: HADOOP-11973
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11973
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 2.6.0
>            Reporter: Gregory Chanan
> I recently added an ACL Provider to the curator framework instance I pass to the ZkDelegationTokenSecretManager,
and notice some strangeness around ACLs.
> I set: "zk-dt-secret-manager.znodeWorkingPath" to:
> "solr/zkdtsm"
> and notice that
> /solr/zkdtsm/
> /solr/zkdtsm/ZKDTSMRoot
> do not have ACLs
> but all the znodes under /solr/zkdtsm/ZKDTSMRoot have ACLs.  From adding some logging,
it looks like the ACLProvider is never called for /solr/zkdtsm and /solr/zkdtsm/ZKDTSMRoot.
 I don't know if that's a Curator or ZkDelegationTokenSecretManager issue.

This message was sent by Atlassian JIRA

View raw message