You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Brook Zhou (JIRA)" <ji...@apache.org> on 2016/08/03 00:06:20 UTC

[jira] [Commented] (YARN-5451) Container localizers that hang are not cleaned up

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

Brook Zhou commented on YARN-5451:
----------------------------------

Is this because the ContainerLocalizer is launched in a separate process from LCE with a timeOutInterval of 0?

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