[
https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14220210#comment-14220210
]
Aaron T. Myers commented on HDFS-7331:
--------------------------------------
In the abstract it's an interesting idea to have all of our counter metrics be
time-bounded, but presently none of them are, and I see no reason that this new
metric should be inconsistent with the rest of them. I also agree with
[~andrew.wang] that by and large operators consume these metrics via tools that
do aggregations and can do their own calculations of occurrences within a time
bound based on sampling, so there may not be much of a need to implement this
functionality directly in Hadoop.
[~wheat9], to be explicit, are you OK with the current patch as-is? I think we
should commit this and thinking about having TTLs for our counter-based metrics
more generally outside of this JIRA.
> Add Datanode network counts to datanode jmx page
> ------------------------------------------------
>
> Key: HDFS-7331
> URL: https://issues.apache.org/jira/browse/HDFS-7331
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: Charles Lamb
> Assignee: Charles Lamb
> Priority: Minor
> Attachments: HDFS-7331.001.patch, HDFS-7331.002.patch,
> HDFS-7331.003.patch, HDFS-7331.004.patch
>
>
> Add per-datanode counts to the datanode jmx page. For example, networkErrors
> could be exposed like this:
> {noformat}
> }, {
> ...
> "DatanodeNetworkCounts" : "{\"dn1\":{\"networkErrors\":1}}",
> ...
> "NamenodeAddresses" :
> "{\"localhost\":\"BP-1103235125-127.0.0.1-1415057084497\"}",
> "VolumeInfo" :
> "{\"/tmp/hadoop-cwl/dfs/data/current\":{\"freeSpace\":3092725760,\"usedSpace\":28672,\"reservedSpace\":0}}",
> "ClusterId" : "CID-4b38f2ae-5e58-4e15-b3cf-3ba3f46e724e"
> }, {
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
