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 Sat, 03 Nov 2012 18:17:12 GMT

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

Kan Zhang commented on HDFS-4056:

bq. I'm trying to implement this improvement in small incremental steps. This patch alone
does not cause a change in behavior for clients on insecure clusters.

That's beside the point. The point is we have agreed on supporting SIMPLE + SIMPLE, a configuration
where clients shouldn't use tokens. Hence, NN's SecretManager isn't always needed and shouldn't
always be started.

bq. Would you please be willing to lift your veto on this jira? At least to a -0?

On technical basis I wouldn't and in fact, I'd also like to revert HADOOP-8783 and HADOOP-8784.
IMHO, they are a step backward and, like this one, not needed for the purpose of HADOOP-8779.
However, I appreciate the fact that you are the one who's working on it and in the interests
of collaboration, I'm willing to modify my vote to -0.9, which Apache defines as "I really
don't like this, but I'm not going to stand in the way if everyone else wants to go ahead
with it." OK? :)
> 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