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

Hanisha Koneru commented on HDFS-13589:
---------------------------------------

Added a patch to return the upgrade status for a normal upgrade (non-rolling).

Some sample outputs of the {{dfsadmin -upgradeStatus}} command are below:
{code:java}
$ hdfs dfsadmin -upgradeStatus
Upgrade finalized for mycluster-node-1/172.18.0.2:8020
Upgrade finalized for mycluster-node-2/172.18.0.3:8020

$ hdfs dfsadmin -upgradeStatus
Upgrade not finalized for mycluster-node-1/172.18.0.2:8020
Upgrade finalized for mycluster-node-2/172.18.0.3:8020

$ hdfs dfsadmin -upgradeStatus
Upgrade finalized for mycluster-node-2/172.18.0.3:8020
upgradeStatus: Call From e6815a2a1257/172.18.0.2 to mycluster-node-1:8020 
failed on connection exception: java.net.ConnectException: Connection refused; 
For more details see: http://wiki.apache.org/hadoop/ConnectionRefused
{code}

> Add dfsAdmin command to query if "upgrade" is finalized
> -------------------------------------------------------
>
>                 Key: HDFS-13589
>                 URL: https://issues.apache.org/jira/browse/HDFS-13589
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: hdfs
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>         Attachments: HDFS-13589.001.patch
>
>
> When we do upgrade on a Namenode (non rollingUpgrade), we should be able to 
> query whether the upgrade has been finalized or not.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to