[
https://issues.apache.org/jira/browse/HDFS-5899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13895355#comment-13895355
]
Arpit Agarwal commented on HDFS-5899:
-------------------------------------
Hi Chris,
{quote}
When ACLs are disabled, ... an fsimage containing an ACL will cause the
NameNode to abort during startup, and ACLs present in the edit log will cause
the NameNode to abort. If ACLs accidentally crept into the fsimage or edits
(i.e. accidentally started with ACLs enabled, but now the admin wants to switch
them off), then the recovery procedure would be to restart with ACLs enabled,
remove all ACLs, save a new checkpoint, and then restart with ACLs disabled.
{quote}
Does it make sense to capture this briefly in the description of
{{dfs.namenode.acls.enabled}}? +1 other than this question.
Config setting checks while processing specific {{FSEditLogOpCodes}} look
somewhat fragile but I have no better suggestion.
{{TestAclConfigFlag}} is a model test!
> Add configuration flag to disable/enable support for ACLs.
> ----------------------------------------------------------
>
> Key: HDFS-5899
> URL: https://issues.apache.org/jira/browse/HDFS-5899
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: namenode
> Affects Versions: HDFS ACLs (HDFS-4685)
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HDFS-5899.1.patch
>
>
> Add a new configuration property that allows administrators to toggle support
> for HDFS ACLs on/off. By default, the flag will be off. This is a
> conservative choice, and administrators interested in using ACLs can enable
> it explicitly.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
