hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HDFS-999) Secondary namenode should login using kerberos if security is configured
Date Wed, 24 Feb 2010 19:21:28 GMT

     [ https://issues.apache.org/jira/browse/HDFS-999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jakob Homan updated HDFS-999:
-----------------------------

    Hadoop Flags: [Reviewed]

+1 on patch. At the moment, we're using the same key for the NN and 2ndNN, but this may change
at some point in the future. Do we want to save ourselves some work in the future and just
create a second key/value pair for the 2ndNN now? It can certainly point to the same values
as the NN now.

> Secondary namenode should login using kerberos if security is configured
> ------------------------------------------------------------------------
>
>                 Key: HDFS-999
>                 URL: https://issues.apache.org/jira/browse/HDFS-999
>             Project: Hadoop HDFS
>          Issue Type: New Feature
>            Reporter: Boris Shkolnik
>            Assignee: Boris Shkolnik
>         Attachments: HDFS-999.patch
>
>
> Right now, if NameNode is configured to use Kerberos, SecondaryNameNode will fail to
start.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message