You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/23 22:05:38 UTC

[jira] [Moved] (YARN-2342) When killing a task, we don't always need to send a subsequent SIGKILL

     [ https://issues.apache.org/jira/browse/YARN-2342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer moved MAPREDUCE-780 to YARN-2342:
--------------------------------------------------

    Issue Type: Improvement  (was: Bug)
           Key: YARN-2342  (was: MAPREDUCE-780)
       Project: Hadoop YARN  (was: Hadoop Map/Reduce)

> When killing a task, we don't always need to send a subsequent SIGKILL
> ----------------------------------------------------------------------
>
>                 Key: YARN-2342
>                 URL: https://issues.apache.org/jira/browse/YARN-2342
>             Project: Hadoop YARN
>          Issue Type: Improvement
>            Reporter: Vinod Kumar Vavilapalli
>              Labels: newbie
>
> In both TaskController/LinuxTaskController, while killing tasks, first a SIGTERM and then a subsequent SIGKILL. We don't need to send the SIGKILL always. It can be avoided when the SIGTERM command (kill pid for process or kill -- -pid for session) returns a non-zero exit code, i.e. when the signal is not sent successfully because process/process group doesn't exist. 'man 2 kill' says exit code is non-zero only when process/process group is not alive or invalid signal is specified or the process doesn't have permissions. The last two don't happen in mapred code.



--
This message was sent by Atlassian JIRA
(v6.2#6252)