[
https://issues.apache.org/jira/browse/YARN-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13631761#comment-13631761
]
Jason Lowe commented on YARN-445:
---------------------------------
Yes, it's an enhancement request to the NM API. I filed it as signaling
containers to generalize the jstack-on-task-timeout feature, at least in the
UNIX sense. I'm not familiar with the Windows APIs, so I'm not sure how (or
if) signals map on that platform. I could see going three different ways on
this for the NM API:
# methods to trigger various features specific to JVMs like jstack, jmap, etc.
# methods to send generalized signals (if there is a reasonable facsimile on
Windows)
# give up trying to generalize the concept and put in the StopContainerRequest
flag
I'd prefer the generalized signal approach if we can come up with a reasonable
mapping for Windows, as this could be useful for non-JVM containers. In any
case, we've had a lot of requests for the ability to trigger jstacks on
containers in various situations, so I'd like to see at least something done in
the NM API to achieve this.
> 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
