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 "Ramya R (JIRA)" <ji...@apache.org> on 2009/10/27 07:08:00 UTC
[jira] Created: (MAPREDUCE-1157) JT UI shows incorrect scheduling
info for failed/killed retired jobs
JT UI shows incorrect scheduling info for failed/killed retired jobs
--------------------------------------------------------------------
Key: MAPREDUCE-1157
URL: https://issues.apache.org/jira/browse/MAPREDUCE-1157
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobtracker
Affects Versions: 0.20.1, 0.21.0
Reporter: Ramya R
Fix For: 0.20.2, 0.21.0
After a failed/killed job retires, the "Job Scheduling Information" section prints a message such as "<running map tasks at the time the job was killed/failed> running map tasks using <running map slots at the time the job was killed/failed> map slots." Instead it should print a message such as "0 running map tasks using 0 map slots"
Same is the case with reduce task/slots.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (MAPREDUCE-1157) JT UI shows incorrect scheduling
info for failed/killed retired jobs
Posted by "Chris Douglas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/MAPREDUCE-1157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chris Douglas updated MAPREDUCE-1157:
-------------------------------------
Fix Version/s: (was: 0.20.2)
(was: 0.21.0)
> JT UI shows incorrect scheduling info for failed/killed retired jobs
> --------------------------------------------------------------------
>
> Key: MAPREDUCE-1157
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1157
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.1, 0.21.0
> Reporter: Ramya R
>
> After a failed/killed job retires, the "Job Scheduling Information" section prints a message such as "<running map tasks at the time the job was killed/failed> running map tasks using <running map slots at the time the job was killed/failed> map slots." Instead it should print a message such as "0 running map tasks using 0 map slots"
> Same is the case with reduce task/slots.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.