[
https://issues.apache.org/jira/browse/HADOOP-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sreekanth Ramakrishnan updated HADOOP-5048:
-------------------------------------------
Attachment: HADOOP-5048-3.patch
Attaching new patch incorporating, Hemanth's comments and Viveks comments:
* Changed initalizedJobs to HashMap to map of job id to job in progress.
* Changed comments in getJobsToInitalize.
* Changed testJobMovementTestCase, the test case now tests for 4 different kind
of job movements which are possible :
** Submission and completion of the job alongwith removal from waiting and
running queue at correct times.
** Submission and failure of the running job, alongwith appropriate movement
and removals.
** Submission and failure of an initialized job but not scheduled alongwith
appropriate removals.
** Submission and failure of a waiting job alongwith appropriate removal.
> Sometimes job is still displayed in jobqueue_details page for long time after
> job was killed.
> ---------------------------------------------------------------------------------------------
>
> Key: HADOOP-5048
> URL: https://issues.apache.org/jira/browse/HADOOP-5048
> Project: Hadoop Core
> Issue Type: Bug
> Components: contrib/capacity-sched
> Reporter: Karam Singh
> Assignee: Sreekanth Ramakrishnan
> Attachments: HADOOP-5048-1.patch, HADOOP-5048-2.patch,
> HADOOP-5048-3.patch
>
>
> When I tried kill all running job, I noticed that were two jobs were listed
> on jobqueue_details.jsp page page as well as they were also listed under
> failed job on jobtracker.jsp page.
> When I checked status of each that was displayed "killed" and Cleanup task
> status as "Successful", but both jobs were also being on jobqueue_details.jsp
> page for longtime e.g up to 10 -15 mins after I restarted JobTracker.
> Before killing the jobs, status of both jobs was running and no task of from
> them was scheduled.
> I noticed this behavior on 3 different occasions. But is this random, not
> always reproducible.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
