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 "Bikas Saha (JIRA)" <ji...@apache.org> on 2013/04/14 23:28:16 UTC

[jira] [Updated] (YARN-445) Ability to signal containers

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

Bikas Saha updated YARN-445:
----------------------------

    Issue Type: Sub-task  (was: New Feature)
        Parent: YARN-386
    
> Ability to signal containers
> ----------------------------
>
>                 Key: YARN-445
>                 URL: https://issues.apache.org/jira/browse/YARN-445
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager
>    Affects Versions: 2.0.5-beta
>            Reporter: Jason Lowe
>
> It would be nice if an ApplicationMaster could send signals to contaniers such as SIGQUIT, SIGUSR1, etc.
> For example, in order to replicate the jstack-on-task-timeout feature implemented by MAPREDUCE-1119 in Hadoop 0.21 the NodeManager needs an interface for sending SIGQUIT to a container.  For that specific feature we could implement it as an additional field in the StopContainerRequest.  However that would not address other potential features like the ability for an AM to trigger jstacks on arbitrary tasks *without* killing them.  The latter feature would be a very useful debugging tool for users who do not have shell access to the nodes.

--
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