[
https://issues.apache.org/jira/browse/HDFS-4056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478279#comment-13478279
]
Daryn Sharp commented on HDFS-4056:
-----------------------------------
bq. the job client will always fetch a NN delegation token for the job
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.
I'd suggest we debate the pros and cons of adding another conf setting for
whether clients will always use tokens with simple auth on the other jiras
linked to the parent of this jira. Fair enough?
> 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
