hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2582) Scope dfs.ha.namenodes config by nameservice
Date Tue, 22 Nov 2011 05:42:41 GMT

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

Todd Lipcon updated HDFS-2582:
------------------------------

    Description: 
HDFS-2231 started the process of adding configuration for HA, but one piece is missing. The
current state of the configuration is, I believe:
{{dfs.ha.namenodes}} - a list of identifiers for HA namenodes
{{dfs.federation.nameservices}} - a list of federated nameservices
{{dfs.namenode.rpc-address[.nameservice-id][.namenode-id]}} - some specific config for the
given namenode. If HA or federation is disabled, the extra components can be elided for backwards
compatibility.

The issue here is that there is no easy way to discern which NN is paired with which other
NN. Additionally, adding a new federated nameservice to a config will require changes to {{dfs.ha.namenodes}}
which makes templating harder. It would be simpler to change {{dfs.ha.namenodes}} to be nameservice-scoped:
{{dfs.ha.namenodes.<nameservice-id>}}.

  was:
HDFS-2231 started the process of adding configuration for HA, but one piece is missing. The
current state of the configuration is, I believe:
{{dfs.ha.namenodes}} - a list of identifiers for HA namenodes
{{dfs.federation.nameservices}} - a list of federated namespaces
{{dfs.namenode.rpc-address[.nameservice-id][.namenode-id]}} - some specific config for the
given namenode. If HA or federation is disabled, the extra components can be elided for backwards
compatibility.

The issue here is that there is no easy way to discern which NN is paired with which other
NN without explicitly. Additionally, adding a new federated namespace to a config will require
changes to {{dfs.ha.namenodes}} which makes templating harder. It would be simpler to change
{{dfs.ha.namenodes}} to be nameservice-scoped: {{dfs.ha.namenodes.<nameservice-id>}}.

        Summary: Scope dfs.ha.namenodes config by nameservice  (was: Scope dfs.ha.namenodes
config by namespace)

Updated description to clarify terminology ("nameservice" instead of "namespace")
                
> Scope dfs.ha.namenodes config by nameservice
> --------------------------------------------
>
>                 Key: HDFS-2582
>                 URL: https://issues.apache.org/jira/browse/HDFS-2582
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: data-node, name-node
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>             Fix For: HA branch (HDFS-1623)
>
>
> HDFS-2231 started the process of adding configuration for HA, but one piece is missing.
The current state of the configuration is, I believe:
> {{dfs.ha.namenodes}} - a list of identifiers for HA namenodes
> {{dfs.federation.nameservices}} - a list of federated nameservices
> {{dfs.namenode.rpc-address[.nameservice-id][.namenode-id]}} - some specific config for
the given namenode. If HA or federation is disabled, the extra components can be elided for
backwards compatibility.
> The issue here is that there is no easy way to discern which NN is paired with which
other NN. Additionally, adding a new federated nameservice to a config will require changes
to {{dfs.ha.namenodes}} which makes templating harder. It would be simpler to change {{dfs.ha.namenodes}}
to be nameservice-scoped: {{dfs.ha.namenodes.<nameservice-id>}}.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message