hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-318) sendSignal in DefaultContainerExecutor causes "invalid options" error
Date Sat, 05 Jan 2013 16:20:12 GMT
Hyunsik Choi created YARN-318:

             Summary: sendSignal in DefaultContainerExecutor causes "invalid options" error
                 Key: YARN-318
                 URL: https://issues.apache.org/jira/browse/YARN-318
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
    Affects Versions: 2.0.2-alpha
         Environment: * OS: MintOS 14
** MintOS 14 is based on ubuntu 12.10. So, this problem may be caused in ubuntu 12.10.
* procp version: procps-ng 3.3.3
* OpenJDK version: 7u9-2.3.3
* Hadoop version: 2.0.2-alpha
            Reporter: Hyunsik Choi

In line 238 of DefaultcontainerExecutor, sendSignal method causes an error when ContainerManagerImpl
tries to kill a container. The command passed to ShellCommandExecutor in sendSignal() was
"kill -0 -12127".

The following message is copied from the detailMessage of the Exception.

kill: invalid option -- '1'

 kill [options] <pid> [...]

 <pid> [...]            send signal to every <pid> listed
 -<signal>, -s, --signal <signal>
                        specify the <signal> to be sent
 -l, --list=[<signal>]  list all signal names, or convert one to a name
 -L, --table            list all signal names in a nice table

 -h, --help     display this help and exit
 -V, --version  output version information and exit

For more details see kill(1).

I investigated a little bit on this problem. I've found that sendSignal works well with traditional
procp (http://procps.sourceforge.net/), whereas it causes such a error with procps-ng (https://fedoraproject.org/wiki/Features/procps-ng)
used in MintOS 14. As you know, 'kill' command is included in procp package in general linux
distributions. When I only change the 'kill' binary into traditional one, stopContainer works

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message