You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Gary Steelman (JIRA)" <ji...@apache.org> on 2014/09/01 23:42:20 UTC

[jira] [Commented] (YARN-2486) FileSystem counters can overflow for large number of readOps, largeReadOps, writeOps

    [ https://issues.apache.org/jira/browse/YARN-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14117741#comment-14117741 ] 

Gary Steelman commented on YARN-2486:
-------------------------------------

I'd really like to see these as long types instead of int, thanks for reporting! Are there other places where counters are int types where we should change them to long types?

> FileSystem counters can overflow for large number of readOps, largeReadOps, writeOps
> ------------------------------------------------------------------------------------
>
>                 Key: YARN-2486
>                 URL: https://issues.apache.org/jira/browse/YARN-2486
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.4.1
>            Reporter: Swapnil Daingade
>            Priority: Minor
>
> The org.apache.hadoop.fs.FileSystem.Statistics.StatisticsData class defines readOps, largeReadOps, writeOps as int. Also the The org.apache.hadoop.fs.FileSystem.Statistics class has methods like getReadOps(), getLargeReadOps() and getWriteOps() that return int. These int values can overflow if the exceed 2^31-1 showing negative values. It would be nice if these can be changed to long.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)