[
https://issues.apache.org/jira/browse/HADOOP-5636?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12710317#action_12710317
]
Karam Singh commented on HADOOP-5636:
-------------------------------------
Submitted a job whose setup task run 3 mins.
When Setup task of jobs is running, go to TT on which setup task is running and
suspend TT process.
Issue hadoop job -kill
Checked that job is moved killed state
Resume TT (TT is process should be resumed at time setup task is complete ).
Without 5636 patch applied -:
Job is switched to running state. Job is not removed from capacity scheduler
queue.
When can see NullPointerException in JobTracker log on assignTask. No new job
is scheduled
With Job patch -:
Job state does not change and Job is removed from capacity-scheduler queue.
No NPE in JobTracker log, and other jobs are getting scheduled.
> Job is left in Running state after a killJob
> --------------------------------------------
>
> Key: HADOOP-5636
> URL: https://issues.apache.org/jira/browse/HADOOP-5636
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Reporter: Amareshwari Sriramadasu
> Assignee: Amar Kamat
> Priority: Critical
> Fix For: 0.20.1
>
> Attachments: HADOOP-5636-v1.0.patch
>
>
> In one scenario, Job was left in Running state forever, when a kill was
> issued after launching job setup task.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
