[
https://issues.apache.org/jira/browse/YARN-7395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16219531#comment-16219531
]
Eric Badger edited comment on YARN-7395 at 10/25/17 9:21 PM:
-------------------------------------------------------------
I'm seeing this on an internal 2.8 build of hadoop with everything underneath
YARN-3611 pulled back. So it is possible that this bug is exclusive to that
environment and not present in 2.9 or 3.0. However, the resource monitoring
seems to be working correctly, it's the docker kill portion that isn't
successful. That's why I believe that this is an issue across 2.9 and 3.0
was (Author: ebadger):
I'm seeing this on an internal 2.8 build of hadoop with everything underneath
YARN-3611 pulled back. So it is possible that this bug is exclusive to that
environment and not present in 2.9 or 3.0.
> NM fails to successfully kill tasks that run over their memory limit
> --------------------------------------------------------------------
>
> Key: YARN-7395
> URL: https://issues.apache.org/jira/browse/YARN-7395
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: yarn
> Reporter: Eric Badger
>
> The NM correctly notes that the container is over its configured limit, but
> then fails to successfully kill the process. So the Docker container AM stays
> around and the job keeps running
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
