[
https://issues.apache.org/jira/browse/YARN-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16637117#comment-16637117
]
Eric Yang commented on YARN-7644:
---------------------------------
[~csingh] The mvn install on root seems like a release branch error. We can
trigger test again after trunk has been fixed. I think ContainerCleanup class
belong to
org.apache.hadoop.yarn.server.nodemanager.containermanager.deletion.task
instead of in
org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher for reusing
existing package structure.
Some checkstyle can be clean up.
[~ebadger] [~jlowe] Do you have any concern in the async task for reapContainer?
> NM gets backed up deleting docker containers
> --------------------------------------------
>
> Key: YARN-7644
> URL: https://issues.apache.org/jira/browse/YARN-7644
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: nodemanager
> Reporter: Eric Badger
> Assignee: Chandni Singh
> Priority: Major
> Labels: Docker
> Attachments: YARN-7644.001.patch
>
>
> We are sending a {{docker stop}} to the docker container with a timeout of 10
> seconds when we shut down a container. If the container does not stop after
> 10 seconds then we force kill it. However, the {{docker stop}} command is a
> blocking call. So in cases where lots of containers don't go down with the
> initial SIGTERM, we have to wait 10+ seconds for the {{docker stop}} to
> return. This ties up the ContainerLaunch handler and so these kill events
> back up. It also appears to be backing up new container launches as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
