[
https://issues.apache.org/jira/browse/HDFS-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478324#comment-13478324
]
Kan Zhang commented on HDFS-4056:
---------------------------------
I think it's more appropriate for me to add this comment here, since I need the
example in my previous comment.
bq. This is the misunderstanding. The patch does not force clients or job
submission to obtain a token. The client simply has the option of requesting
and using a token, but the client can still continue to run with no token as it
does today.
But without the option to specify what the job client should do when SIMPLE is
specified for initial auth, it can be coded only one way (either always fetch
tokens or never). Do you see my point?
> Always start the NN's SecretManager
> -----------------------------------
>
> Key: HDFS-4056
> URL: https://issues.apache.org/jira/browse/HDFS-4056
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0, 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HDFS-4056.patch
>
>
> To support the ability to use tokens regardless of whether kerberos is
> enabled, the NN's secret manager should always be started.
--
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
