hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eli Collins (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-2918) HA: Update HA docs to cover dfsadmin
Date Thu, 09 Feb 2012 05:11:59 GMT

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

Eli Collins updated HDFS-2918:
------------------------------

    Summary: HA: Update HA docs to cover dfsadmin  (was: HA: dfsadmin should failover like
other clients)

Yup, I filed HDFS-2922 for that with a patch. We need to update the HA docs to cover the behavior
of dfsadmin (eg which operations failover, which don't and why, which should be performed
only on the active, which are OK to do on the standby). Once we can name the specific namenode
IDs in dfsadmin (HDFS-2916) I think it will be more clear / easy for users. Re-purposing this
jira to update the docs.
                
> HA: Update HA docs to cover dfsadmin
> ------------------------------------
>
>                 Key: HDFS-2918
>                 URL: https://issues.apache.org/jira/browse/HDFS-2918
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ha
>    Affects Versions: HA branch (HDFS-1623)
>            Reporter: Eli Collins
>            Assignee: Eli Collins
>
> dfsadmin currently always uses the first namenode rather than failing over. It should
failover like other clients, unless fs specifies a specific namenode.
> {noformat}
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs haadmin -failover nn1 nn2
> Failover from nn1 to nn2 successful
> # nn2 is 8022
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs dfsadmin -fs localhost:8022 -safemode enter
> Safe mode is ON
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs dfsadmin -safemode get 
> Safe mode is OFF
> hadoop-0.24.0-SNAPSHOT $ ./bin/hdfs dfsadmin -fs localhost:8022 -safemode get
> Safe mode is ON
> {noformat}

--
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