You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Matt Foley (Updated) (JIRA)" <ji...@apache.org> on 2011/10/19 03:15:11 UTC
[jira] [Updated] (MAPREDUCE-486) JobTracker web UI counts
COMMIT_PENDING tasks as Running
[ https://issues.apache.org/jira/browse/MAPREDUCE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Foley updated MAPREDUCE-486:
---------------------------------
Target Version/s: 0.20.206.0
Fix Version/s: (was: 0.20.205.0)
> 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