[
https://issues.apache.org/jira/browse/HDFS-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12897349#action_12897349
]
Hong Tang commented on HDFS-1339:
---------------------------------
If you only use it to calculate rates of such operations (such as ops/s or
ops/hour), it probably does not matter whether using long or int.
> NameNodeMetrics should use MetricsTimeVaryingLong
> --------------------------------------------------
>
> Key: HDFS-1339
> URL: https://issues.apache.org/jira/browse/HDFS-1339
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Reporter: Scott Chen
> Assignee: Scott Chen
> Priority: Minor
> Attachments: HDFS-1339.txt
>
>
> NameNodeMetrics uses MetricsTimeVaryingInt. We see that FileInfoOps and
> GetBlockLocations overflow in our cluster.
> Using MetricsTimeVaryingLong will easily solve this problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
