hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amar Kamat (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5048) Sometimes job is still displayed in jobqueue_details page for long time after job was killed.
Date Fri, 16 Jan 2009 04:11:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-5048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12664400#action_12664400

Amar Kamat commented on HADOOP-5048:

bq. In case of zero tasks assigned to a job. The job's initTask() is called. Then in next
polling cycle the list of JobInProgress on which initTasks() has been called is checked and
the finished jobs are removed from wait queue. 
What happens to the jobs in the wait-queue? I guess in this jira we expect that to happen
via the job-state-change-event which wont happen, no? 

> Sometimes job is still displayed in jobqueue_details page for long time after job was
> ---------------------------------------------------------------------------------------------
>                 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
> 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
> 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.

View raw message