hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HDFS-1721) Hdfs Federation: Configuration for principal names should not be namenode specific.
Date Thu, 03 Mar 2011 23:24:36 GMT

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

Suresh Srinivas commented on HDFS-1721:

+1 for the patch.

> Hdfs Federation: Configuration for principal names should not be namenode specific.
> -----------------------------------------------------------------------------------
>                 Key: HDFS-1721
>                 URL: https://issues.apache.org/jira/browse/HDFS-1721
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: name-node
>    Affects Versions: Federation Branch
>            Reporter: Jitendra Nath Pandey
>            Assignee: Jitendra Nath Pandey
>             Fix For: Federation Branch
>         Attachments: HDFS-1721.1.patch, HDFS-1721.2.patch
> The principal names in the configuration for namenode, secondary namenode, backup namenode,
need not be namenode specific, i.e. they need not be configured with keys suffixed with nameserviceId.
> This is because if principals were namenode specific, we would need a mechanism to figure
out nameserviceId (to get the namenode specific principal) from fqdn of the files at the client.
>  A simpler approach is to use _HOST pattern in the principal names. Hadoop RPC supports
replacing the _HOST in the principal with the hostname of the service. Using this approach
we need only one principal configuration for all namenodes and similarly one for all secondary
namenodes or backup namenodes. 

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message