hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chandni Singh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7644) NM gets backed up deleting docker containers
Date Tue, 21 Aug 2018 22:26:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16588083#comment-16588083
] 

Chandni Singh commented on YARN-7644:
-------------------------------------

[~ebadger] I would like to work on this issue. Please re-assign to me if you are not working
on it.

> 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: Eric Badger
>            Priority: Major
>              Labels: Docker
>
> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message