Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 20 Jan 2012 08:44:41 +0000 (UTC)
From: "Devaraj K (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1811792795.59432.1327049081189.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-486) JobTracker web UI counts
 COMMIT_PENDING tasks as Running
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Devaraj K commented on MAPREDUCE-486:
-------------------------------------

Recently I also have faced the same thing, and confused that why it is taking more than the configured capacity. After debugging the code, came to know that extra tasks are only in commit pending state. It is better to have this in the UI to avoid confusion. 

Patch looks good to me.
                
> JobTracker web UI counts COMMIT_PENDING tasks as Running
> --------------------------------------------------------
>
>                 Key: MAPREDUCE-486
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-486
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.20.2
>            Reporter: Todd Lipcon
>            Assignee: Harsh J
>            Priority: Minor
>         Attachments: 0.20-MAPREDUCE-486.r1.diff, After Commit_pending column.png, Before Commit_pending column.png, runcount.jar, runcount.tar.gz
>
>
> In jobdetails.jsp, tasks in COMMIT_PENDING state are listed as "Running". I propose creating another column in this table for COMMIT_PENDING tasks, since users find it confusing that a given job can have more tasks "Running" than their total cluster capacity.

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