hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahadev konar (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3822) TestJobCounters is failing intermittently on trunk and 0.23.
Date Mon, 06 Feb 2012 23:09:02 GMT

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

Mahadev konar commented on MAPREDUCE-3822:
------------------------------------------

Found the issue. This looks like more of a FileSystem Statistics issue. Here is the scenario,
when creating FileSystems like FilterFileSystem/RawLocalFileSystem, LocalFileSystem, they
all use the same uri (file://). On a getAllStatistics() it will return all the stats for all
3 file systems but only one of them is the true filesystem whose stats are being updated.
When we update our counters in Task.java (updateCounters), we just use the scheme and set
the counter values. So there is a race condition on which order you get the FileSystem Stats
in which might lead to a value of 0 for FS counters. We could fix this in Common or just do
a hack on checking non zero counters which we consider as the right counters. Not sure. 

Given that this is only on localfilesystem, I think we can skip on this for 0.23.1.
                
> TestJobCounters is failing intermittently on trunk and 0.23.
> ------------------------------------------------------------
>
>                 Key: MAPREDUCE-3822
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3822
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>            Reporter: Mahadev konar
>            Assignee: Mahadev konar
>            Priority: Critical
>             Fix For: 0.23.1
>
>
> TestJobCounters fails sometimes on trunk. I have tracked it down to stats issue in FileSystem.
Still working on it. 

--
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

        

Mime
View raw message