[
https://issues.apache.org/jira/browse/YARN-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15457917#comment-15457917
]
Jian He commented on YARN-5615:
-------------------------------
HADOOP-11552 is one solution to this. NMClient waits until the container is
actually stopped/started and then executes the callback handler
> onContainerStarted/Stopped callback handler in NMClientAsync does not
> necessarily mean container started/stopped
> ----------------------------------------------------------------------------------------------------------------
>
> Key: YARN-5615
> URL: https://issues.apache.org/jira/browse/YARN-5615
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Jian He
>
> The onContainerStarted, onContainerStopped callback handler in the
> NMClientAsync does not mean the container is started/stopped. Based on the
> implementation, it only means that the startContainer/stopContainer call has
> returned. NM is still on the way to start/stop container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
