[jira] Created: (MAPREDUCE-780) When killing a task, we don't always need to send a subsequent SIGKILL

["Vinod K V (JIRA)" <ji...@apache.org>]

When killing a task, we don't always need to send a subsequent SIGKILL
----------------------------------------------------------------------

                 Key: MAPREDUCE-780
                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-780
             Project: Hadoop Map/Reduce
          Issue Type: Bug
            Reporter: Vinod K V


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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.