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

Yiqun Lin commented on HDFS-10436:
----------------------------------

Hi, [~aw], the comments that I gave before seemed not correct. I am sorry for 
that. The dfs.block.access.token.enable default on will let the method 
{{createBlockTokenSecretManager}} return a new {{BlockTokenSecretManager}} and 
then it means that BlockToken was enabled in {{BlockManager}}. It will change 
the existed logic.

> dfs.block.access.token.enable should default on when security is !simple
> ------------------------------------------------------------------------
>
>                 Key: HDFS-10436
>                 URL: https://issues.apache.org/jira/browse/HDFS-10436
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode, namenode
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Allen Wittenauer
>            Assignee: Yiqun Lin
>         Attachments: HDFS-10436.001.patch
>
>
> Unless there is a valid configuration where dfs.block.access.token.enable is 
> off and security is on, then rather than shutdown we should just enable the 
> block access tokens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to