[
https://issues.apache.org/jira/browse/MAPREDUCE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Harsh J updated MAPREDUCE-486:
------------------------------
Attachment: 0.20-MAPREDUCE-486.r1.diff
After Commit_pending column.png
Before Commit_pending column.png
runcount.tar.gz
runcount.jar
Finally got around to writing something for this.
(Patch for 0.20-security this round, will work on 0.23+ requirement in a bit)
- runcount.jar is a test MR program with 1-min sleeping OutputCommitter. Its
the one with which I've taken before/after screenies.
- runcount.tar.gz is the source file for the above, if anyone's interested.
- Added a column 'Commit Pending' per the original idea since it made more
sense than hiding away the count (And causing math panics)
- The check done to determine is TIP.isOnlyCommitPending();
- Updated jobdetails.jsp to show this properly, and manually tested the patch
(as per screenshots).
- Couldn't really update and form a new page on jobtasks.jsp page cause
COMMIT_PENDING isn't really a TIPStatus I can filter upon. Thus for now, it
would link to RUNNING tasks page itself.
> 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
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
