[
https://issues.apache.org/jira/browse/HADOOP-1351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510079
]
Enis Soztutar commented on HADOOP-1351:
---------------------------------------
Thanks Arun for the suggestion,
> mark the task as FAILED (and not KILLED since you want this attempt to count
> against the job).
Actually i think, we should label the task as KILLED, rather than FAILED, since
killing is a task is quite an explicit action done by the user examining the
system so she may prefer seeing the task as KILLED (Although in the similar
case for killing jobs we do not have KILLED status for a job, so killed jobs
appear as FAILED). Also, regarding our use cases, we do not want to "black
label" the machine for killed task ({{machinesWhereFailed}}), that's why i have
written {{taskKilled}} instead of using {{incompleteSubTask}}.
I will look deeper into using {{TaskInProgress.shouldCloseForClosedJob }} and
{{tasksReportedClosed}}. I bet having a generic DFA implementation will benefit
us in this.
> Want to kill a particular task or attempt
> -----------------------------------------
>
> Key: HADOOP-1351
> URL: https://issues.apache.org/jira/browse/HADOOP-1351
> Project: Hadoop
> Issue Type: New Feature
> Components: mapred
> Affects Versions: 0.12.3
> Reporter: Owen O'Malley
> Assignee: Enis Soztutar
> Fix For: 0.14.0
>
> Attachments: killTask_v1.0.1.patch
>
>
> It would be convenient to be able to kill a particular task or attempt from
> the command line. It would look like:
> bin/hadoop job -kill-task tip_0001_m_000000
> bin/hadoop job -kill-attempt task_0001_m_000000_0
> This would allow the user to tell the system to stop a particular task or
> attempt without having to restart a task tracker.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
