[
https://issues.apache.org/jira/browse/HDFS-7331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14215587#comment-14215587
]
Haohui Mai commented on HDFS-7331:
----------------------------------
Thinking about it a little bit more, from a operational point of view maybe it
is important to limit the TTL of these counts.
If I understand correctly, the current patch does not reset the counts unless
the DN is restarted. The number of the network failures since the last 24
hours, last week, etc. might be more valuable.
Therefore I think it might be more appropriate to limit the TTL of the counts
(which should be configurable), instead of bounding the maximum size of the map
(which should be effectively bounded by the TTL anyway).
> 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)
