[
https://issues.apache.org/jira/browse/HDFS-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13702089#comment-13702089
]
Suresh Srinivas commented on HDFS-4278:
---------------------------------------
bq. Suresh - Given the security won't work without it, why log an ERROR thats a
step more longer to catch?
I am okay with it. Perhaps we could log a warning DFS_BLOCK_ACCESS_TOKEN_ENABLE
is turned off and it is automatically being turned on.
How do you make it work for testing purpose? I am against doing this by adding
conditional code and variables with restricted visibility and unnecessary code
complication. In that case, I would rather error out on the user about
incompatible configuration than doing things automatically.
> The DFS_BLOCK_ACCESS_TOKEN_ENABLE config should be automatically turned on
> when security is enabled.
> ----------------------------------------------------------------------------------------------------
>
> Key: HDFS-4278
> URL: https://issues.apache.org/jira/browse/HDFS-4278
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode, namenode
> Affects Versions: 2.0.0-alpha
> Reporter: Harsh J
> Labels: newbie
> Attachments: HDFS-4278.patch
>
>
> When enabling security, one has to manually enable the config
> DFS_BLOCK_ACCESS_TOKEN_ENABLE (dfs.block.access.token.enable). Since these
> two are coupled, we could make it turn itself on automatically if we find
> security to be enabled.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
