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 "Ming Ma (JIRA)" <ji...@apache.org> on 2015/09/15 03:05:46 UTC

[jira] [Updated] (YARN-1897) Define SignalContainerRequest and SignalContainerResponse

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

Ming Ma updated YARN-1897:
--------------------------
    Attachment: YARN-1897-5.patch

Based on the offline discussion with [~djp] [~stevel@apache.org] [~xgong] w.r.t. to YARN-4131 and signal container functionality, we decided to speed up the open source effort for signal container functionality. Instead of defining a comprehensive API to all scenarios, we prefer to addressing immediate scenarios first.

Here is the draft patch that provides the core signal container functionality so that users can use YARN CLI to capture thread dump of a container or kill a container. Things that will be covered by other jiras are:

* WebUI support.
* Thread dump support on windows.
* Batch support so that AM or applications can send several ordered requests at once.
* Allow applications to specify custom command and have NM run it against the container.

> Define SignalContainerRequest and SignalContainerResponse
> ---------------------------------------------------------
>
>                 Key: YARN-1897
>                 URL: https://issues.apache.org/jira/browse/YARN-1897
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: api
>            Reporter: Ming Ma
>            Assignee: Ming Ma
>         Attachments: YARN-1897-2.patch, YARN-1897-3.patch, YARN-1897-4.patch, YARN-1897-5.patch, YARN-1897.1.patch
>
>
> We need to define SignalContainerRequest and SignalContainerResponse first as they are needed by other sub tasks. SignalContainerRequest should use OS-independent commands and provide a way to application to specify "reason" for diagnosis. SignalContainerResponse might be empty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)