[
https://issues.apache.org/jira/browse/HDFS-2808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Collins updated HDFS-2808:
------------------------------
Attachment: hdfs-2808.txt
As part of switching from host:ipc targets to logical namenode IDs we need to
know the namespace to use to resolve the namenode IDs. If federation is not
configured there will be just on namespace configured so we can use it
automatically. Otherwise however we'll need to determine which nameservice to
use. Some options:
- Require the ns be passed as part of the target eg <nsId.nnId>. I don't like
this option since it allows for different namespaces to be specified in
operations like failover.
- Require a nameservice be passed explicitly (via
dfs.federation.nameservice.id) in the config used to run the haadmin command. I
don't like this option as it requires using a different config for haadmin.
- Rework HAadmin to work more like a typical shell, ie "bin/hdfs haadmin
[OPTION].. [ARG]..." instead of requiring commands start with a slash and are
always the first argument.
- Rework HAAdmin to handle generic options like dfsadmin
eg bin/hdfs dfsadmin [genericOptions] [commandOptions]
I think I'll go with the latter to be consistent with dfsadmin.
In the meantime here's a patch which works as long as there's only one
configured namespace. I'll rework haadmin in another change and then layer this
change atop it.
> HA: Use logical names in haadmin
> --------------------------------
>
> Key: HDFS-2808
> URL: https://issues.apache.org/jira/browse/HDFS-2808
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Components: ha
> Affects Versions: HA branch (HDFS-1623)
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hdfs-2808.txt
>
>
> Currently haadmin services are specified by host:ipcport, we should use a
> logical names instead, eg dfs.ha.namenode.id when the service is a namenode.
--
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
