[
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
Patch attached. Previous patch plus introduces an haadmin wide nameservice
parameter, which can be moved to DFSHAAdmin if it turns out to not be generic.
I tested all the haadmin commands using logical names. Here's example usage
with the new nameservice option.
{noformat}
# 1 nameservice in the config
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -getServiceState nn1
active
# 1 nameservice in the config, specified
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -ns ha-nn-uri -getServiceState nn1
active
# invalid ns specified
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -ns invalid -getServiceState nn1
Illegal argument: Unable to determine service address for namenode 'nn1'
# 2 nameservices in the config
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -getServiceState nn1
Illegal argument: Unable to determine service address for namenode 'nn1'
# 2 nameservices in the config, 1 specified
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -ns ha-nn-uri -getServiceState nn1
active
# failover using a namespace
hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -ns ha-nn-uri -failover nn1 nn2
Failover from nn1 to nn2 successful
{noformat}
> 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, 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
