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

Kihwal Lee commented on HDFS-402:
---------------------------------

I am not suggesting that it is the right way, but merely pointing out that 
people easily lose interest/motivation if "it's no longer my immediate 
problem."  Do you think Hadoop needs to provide a basic rolling upgrade tool in 
order to call rolling upgrade feature complete?  If so, why don't you file a 
jira and put this one under that?

> Display the server version in dfsadmin -report
> ----------------------------------------------
>
>                 Key: HDFS-402
>                 URL: https://issues.apache.org/jira/browse/HDFS-402
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Jakob Homan
>            Assignee: Uma Maheswara Rao G
>            Priority: Minor
>              Labels: newbie
>         Attachments: HDFS-402.patch, HDFS-402.patch, HDFS-402.patch, 
> hdfs-402.txt
>
>
> As part of HADOOP-5094, it was requested to include the server version in the 
> dfsadmin -report, to avoid the need to screen scrape to get this information:
> bq. Please do provide the server version, so there is a quick and non-taxing 
> way of determine what is the current running version on the namenode.
> Currently there is nothing in the dfs client protocol to query this 
> information.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to