[
https://issues.apache.org/jira/browse/YARN-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15406159#comment-15406159
]
Varun Vasudev commented on YARN-5451:
-------------------------------------
bq. The localizer should be tracked like containers are tracked so we can
control them like we can control containers.
+1. This really becomes a problem for containers with large sized
resources(like docker). We have to be able to kill a localizer.
> Container localizers that hang are not cleaned up
> -------------------------------------------------
>
> Key: YARN-5451
> URL: https://issues.apache.org/jira/browse/YARN-5451
> Project: Hadoop YARN
> Issue Type: Bug
> Components: nodemanager
> Affects Versions: 2.6.0
> Reporter: Jason Lowe
>
> I ran across an old, rogue process on one of our nodes. It apparently was a
> container localizer that somehow entered an infinite loop during startup.
> The NM never cleaned up this broken localizer, so it happily ran forever.
> The NM needs to do a better job of tracking localizers, including killing
> them if they appear to be hung/broken.
--
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
