[
https://issues.apache.org/jira/browse/HDFS-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13178332#comment-13178332
]
Harsh J commented on HDFS-402:
------------------------------
Hey Uma,
Yep I read that. My comments were just for the patch :)
I'm just thinking if its worth sending that version info (beyond RPC version
which we already do) for just this purpose.
Second point is that with metrics and such data exposed now, that should be the
direction we should be pushing the monitoring at. I doubt if "dfsadmin -report"
even stands close to that, though it is nifty as it stands today and shouldn't
be removed. Just shouldn't be suggested to be used for monitoring, or checking,
over the metrics stuff?
What would you say for this approach vs. improved documentation and
stabilization of the metrics information we publish?
> Display the server version in dfsadmin -report
> ----------------------------------------------
>
> Key: HDFS-402
> URL: https://issues.apache.org/jira/browse/HDFS-402
> Project: Hadoop HDFS
> Issue Type: Wish
> Reporter: Jakob Homan
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-402.patch
>
>
> 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 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
