[ https://issues.apache.org/jira/browse/HDFS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15060371#comment-15060371 ]
Allen Wittenauer commented on HDFS-402: --------------------------------------- bq. It is perhaps because there are already other ways to get the relevant information. E.g., I do not have any experience with Ambari, but it must be checking and reporting versions through jmx, etc. In other words, rather than having Hadoop's built-in reporting mechanism actually work and give useful information, we should require a third party tool or make ops teams write their own reporting tools even though it's going to be an absolutely common request/requirement after rolling upgrades become more common place? > 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)