hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arpit Agarwal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5925) ACL configuration flag must only reject ACL API calls, not ACLs present in fsimage or edits.
Date Tue, 11 Feb 2014 21:33:20 GMT

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

Arpit Agarwal commented on HDFS-5925:
-------------------------------------

Hi Chris,

Not sure you need to remove {{testEditLog}}. We can just change the test to verify that the
restart succeeds after ACLs are enabled. Also we can extend it to make sure that the restart
succeeds after saving a checkpoint with ACL entries. What do you think?

+1 otherwise.

> ACL configuration flag must only reject ACL API calls, not ACLs present in fsimage or
edits.
> --------------------------------------------------------------------------------------------
>
>                 Key: HDFS-5925
>                 URL: https://issues.apache.org/jira/browse/HDFS-5925
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: namenode
>    Affects Versions: HDFS ACLs (HDFS-4685)
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-5925.1.patch
>
>
> In follow-up discussion on HDFS-5899, we decided that it would cause less harm to administrators
if setting {{dfs.namenode.acls.enabled}} to false only causes ACL API calls to be rejected.
 Existing ACLs found in fsimage or edits will be loaded and enforced.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message