hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hemanth Yamijala (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 Thu, 15 Jan 2009 17:10:59 GMT

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

Hemanth Yamijala commented on HADOOP-5048:

bq. JobQueuesManager should be responsible for removing a job from both the run and wait queue
when the job completes.

While reviewing HADOOP-4513, I had commented on this [here|http://issues.apache.org/jira/browse/HADOOP-4513?focusedCommentId=12648951#action_12648951]
as follows:

bq. I am thinking removal of completed jobs from the 'jobqueue' must also be done in jobCompleted,
and not from the poller. This keeps it simple to understand.

Sreekanth, do you remember why we did not do this in the end ?

> 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