[
https://issues.apache.org/jira/browse/HDFS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060341#comment-15060341
]
Allen Wittenauer edited comment on HDFS-402 at 12/16/15 5:21 PM:
-----------------------------------------------------------------
With rolling upgrade, this is very important now: at least, to reflect the
datanode version. The fact that this wasn't completed as part of that JIRA
goes to the level of 'fit and finish' that seems to be permeating Hadoop the
past few years.
was (Author: aw):
With rolling upgrade, this is very important now. The fact that this wasn't
completed as part of that JIRA goes to the level of 'fit and finish' that seems
to be permeating Hadoop the past few years.
> 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)
