hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2264) Job status exceeds 100% in some cases
Date Fri, 20 May 2011 15:34:47 GMT

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

Devaraj K commented on MAPREDUCE-2264:
--------------------------------------

It was considering compressed bytes size for calculating the totalBytes because of this it
is showing the progress as more than 100%. 
Provided patch consider the uncompressed size of the data for calculating the progress.


> Job status exceeds 100% in some cases 
> --------------------------------------
>
>                 Key: MAPREDUCE-2264
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2264
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>            Reporter: Adam Kramer
>            Assignee: Devaraj K
>             Fix For: 0.20.4, 0.23.0
>
>         Attachments: MAPREDUCE-2264-0.20.3.patch, MAPREDUCE-2264-trunk.patch, more than
100%.bmp
>
>
> I'm looking now at my jobtracker's list of running reduce tasks. One of them is 120.05%
complete, the other is 107.28% complete.
> I understand that these numbers are estimates, but there is no case in which an estimate
of 100% for a non-complete task is better than an estimate of 99.99%, nor is there any case
in which an estimate greater than 100% is valid.
> I suggest that whatever logic is computing these set 99.99% as a hard maximum.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message