Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Sat, 8 Mar 2014 03:46:51 +0000 (UTC)
From: "Ming Ma (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12634978.1362247440219.28583.1394250411334@arcas>
In-Reply-To: <JIRA.12634978.1362247440219@arcas>
References: <JIRA.12634978.1362247440219@arcas>
Subject: [jira] [Updated] (YARN-445) Ability to signal containers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ming Ma updated YARN-445:
-------------------------

    Issue Type: Task  (was: Sub-task)
        Parent:     (was: YARN-386)

> Ability to signal containers
> ----------------------------
>
>                 Key: YARN-445
>                 URL: https://issues.apache.org/jira/browse/YARN-445
>             Project: Hadoop YARN
>          Issue Type: Task
>          Components: nodemanager
>            Reporter: Jason Lowe
>            Assignee: Andrey Klochkov
>         Attachments: MRJob.png, MRTasks.png, YARN-445--n2.patch, YARN-445--n3.patch, YARN-445--n4.patch, YARN-445.patch, YARNContainers.png
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)