[
https://issues.apache.org/jira/browse/YARN-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13962221#comment-13962221
]
Ming Ma commented on YARN-1897:
-------------------------------
+1 for SignalContainerRequest. For SignalContainerResponse, what is the
semantics of isCMDCompleted? If we want to support synchronous signal
container call and this flag indicates whether ContainerExecutor has signaled
on the container successfully, that will require RM to wait for the response
from NM after NM finishes the work; it implies ApplicationClientProtocol's
signalContainer method will hold up a RPC handler for some period of time; we
can have some time out or rate limiting on signalContainer call to make sure
applications won't be able to consume all RM's RPC handlers. If isCMDCompleted
means if the command has been submitted to RM successfully, then it is ok; or
we can use exception to indicate failure of the request.
> 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
>
> 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)
