hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Junping Du (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (YARN-2342) When killing a task, we don't always need to send a subsequent SIGKILL
Date Fri, 01 May 2015 19:35:09 GMT

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

Junping Du reassigned YARN-2342:
--------------------------------

    Assignee: Junping Du

> 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
>            Assignee: Junping Du
>              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.3.4#6332)

Mime
View raw message