hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jian He (JIRA)" <j...@apache.org>
Subject [jira] [Created] (YARN-5615) NMClienAsynct#CallbackHandler#onContainerStarted/Stopped does not necessarily mean container started/stopped
Date Fri, 02 Sep 2016 08:21:20 GMT
Jian He created YARN-5615:
-----------------------------

             Summary: NMClienAsynct#CallbackHandler#onContainerStarted/Stopped 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message