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 "Arun Suresh (JIRA)" <ji...@apache.org> on 2015/05/19 20:29:00 UTC

[jira] [Updated] (HADOOP-11973) Ensure ZkDelegationTokenSecretManager namespace znodes get created with ACLs

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

Arun Suresh updated HADOOP-11973:
---------------------------------
    Fix Version/s: 2.7.1

> Ensure ZkDelegationTokenSecretManager namespace znodes get created with 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
>            Assignee: Gregory Chanan
>             Fix For: 2.7.1
>
>         Attachments: HADOOP-11973.patch, HADOOP-11973v2.patch
>
>
> 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
(v6.3.4#6332)