hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kan Zhang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4056) Always start the NN's SecretManager
Date Thu, 01 Nov 2012 03:39:12 GMT

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

Kan Zhang commented on HDFS-4056:

bq. Yes, it should work if you fetch the token yourself.

As far as I know, that is not by design.

bq. What would be the confusion?

Suppose some clients are configured to use tokens, some don't. How do you make sure they did
what they are supposed to do? Or you don't care? If a client happens to use a Hadoop conf
that says "use tokens", it will fetch and use them; otherwise, it won't. Either way it works.
It's hard to reason about cluster behavior, that is what I meant by confusing.

bq. I don't recall a problem ever being root-caused to a stale token file.

May I quote "Past performance is no guarantee of future results"? :)
> 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

View raw message