hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uma Maheswara Rao G (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-2918) HA: dfsadmin should failover like other clients
Date Thu, 09 Feb 2012 04:20:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-2918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13204242#comment-13204242
] 

Uma Maheswara Rao G commented on HDFS-2918:
-------------------------------------------

Hi Eli,
 I spent some time on this issue. I dont see any problem with DFSAdmin.

{noformat}
2012-02-09 09:11:29,282 WARN  retry.RetryInvocationHandler (RetryInvocationHandler.java:invoke(106))
- Exception while invoking getStats of class org.apache.hadoop.hdfs.protocolPB.ClientNamenodeProtocolTranslatorPB
after 0 *fail over attempts. Trying to fail over immediately.*
Configured Capacity: 190744240128 (177.64 GB)
Present Capacity: 74658306048 (69.53 GB)
DFS Remaining: 74658299904 (69.53 GB)
DFS Used: 6144 (6 KB)
DFS Used%: 0%
Under replicated blocks: 0
Blocks with corrupt replicas: 0
Missing blocks: 0

-------------------------------------------------
Datanodes available: 3 (3 total, 0 dead)
{noformat}

The problem with the API categeory from Namenode. Currently safemode API are allowing on standby
also. That is tyhe rason it won't do any failover. Otherwise DFSAdmin uses just not FileSystem
object to invoke APIs. So, it should be able to do failover normally if we configure HA related
configurations.

Addressing TODO in NameNodeRPCServer should solve this issue.
{quote}
// TODO:HA decide on OperationCategory for this
{quote}
                
> HA: dfsadmin should failover like other clients
> -----------------------------------------------
>
>                 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