[
https://issues.apache.org/jira/browse/YARN-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004166#comment-14004166
]
Ming Ma commented on YARN-1897:
-------------------------------
Chatted with Gera offline. The definition of SignalContainer* APIs is needed
for other subtasks including YARN-1515. So we will resolve SignalContainer*
APIs issues in this jira. After it is done, other subtasks can continue. Here
are couple open issues.
1. Support for a list of containers. The latest patch in this jira just
supports a flat list of signalContainerRequest, regardless if they are from the
same containers or not. Gera's patch in YARN-1515 groups all commands under the
same container together via signalContainerRequest.getSignals(). Either
approach works. I don't have strong preference either way given the most common
use case is for single container; although signalContainers is more consistent
with startContainers.
2. Support for "SIGTERM + delay + SIGKILL" used in stopContainers. Latest
YARN-1515 introduces "Pause" method so that containers can pause in between
signals. We need something like that to support YARN-1515 scenario. Or we can
provide some new SignalContainerCommand like "sleep".
Really appreciate any comments on this.
> 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.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.2#6252)
