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 Thu, 24 Nov 2011 01:52:43 GMT

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

Todd Lipcon updated HDFS-2582:

    Attachment: hdfs-2582.txt

Here's a patch implementing the proposal.

There's one TODO in there for fixing TestGetConf - I'm working on fixing that now. 

I haven't run all of the unit tests yet, but I did run some of the federation-related tests
as well as some of the HA-related tests and they pass. I also ran a selection of general HDFS
tests and they pass.

The patch does introduce some more TODOs in places like the balancer, where we are currently
doing some custom RPC connections to NNs -- will file a followup JIRA for that when this is
> 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)
>         Attachments: hdfs-2582.txt
> 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


View raw message