[
https://issues.apache.org/jira/browse/MAPREDUCE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13564993#comment-13564993
]
Hadoop QA commented on MAPREDUCE-2264:
--------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12566880/MAPREDUCE-2264-trunk-5.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 1 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 javadoc{color}. The javadoc tool did not generate any
warning messages.
{color:green}+1 eclipse:eclipse{color}. The patch built with
eclipse:eclipse.
{color:green}+1 findbugs{color}. The patch does not introduce any new
Findbugs (version 1.3.9) warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-core.
{color:green}+1 contrib tests{color}. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3288//testReport/
Console output:
https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/3288//console
This message is automatically generated.
> 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
> Affects Versions: 0.20.2, 0.20.205.0
> Reporter: Adam Kramer
> Assignee: Devaraj K
> Labels: critical-0.22.0
> Fix For: 1.2.0, 2.0.3-alpha
>
> Attachments: MAPREDUCE-2264-0.20.205-1.patch,
> MAPREDUCE-2264-0.20.205.patch, MAPREDUCE-2264-0.20.3.patch,
> MAPREDUCE-2264-branch-1-1.patch, MAPREDUCE-2264-branch-1-2.patch,
> MAPREDUCE-2264-branch-1.patch, MAPREDUCE-2264-trunk-1.patch,
> MAPREDUCE-2264-trunk-1.patch, MAPREDUCE-2264-trunk-2.patch,
> MAPREDUCE-2264-trunk-3.patch, MAPREDUCE-2264-trunk-4.patch,
> MAPREDUCE-2264-trunk-5.patch, MAPREDUCE-2264-trunk-5.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
