Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 20 May 2011 15:20:47 +0000 (UTC)
From: "Devaraj K (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1008815389.30677.1305904847744.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: <7041408.361591294972126934.JavaMail.jira@thor>
Subject: [jira] [Updated] (MAPREDUCE-2264) Job status exceeds 100% in some
 cases
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/MAPREDUCE-2264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Devaraj K updated MAPREDUCE-2264:
---------------------------------

    Attachment: MAPREDUCE-2264-trunk.patch
                MAPREDUCE-2264-0.20.3.patch

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