[ https://issues.apache.org/jira/browse/YARN-5615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jian He updated YARN-5615: -------------------------- Summary: onContainerStarted/Stopped callback handler in NMClientAsync does not necessarily mean container started/stopped (was: NMClienAsynct#CallbackHandler#onContainerStarted/Stopped does not necessarily mean container started/stopped) > 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