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 "wangxiangchun (Jira)" <ji...@apache.org> on 2019/11/06 04:28:00 UTC

[jira] [Updated] (YARN-9955) LogAggregationService Thread OOM

     [ https://issues.apache.org/jira/browse/YARN-9955?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

wangxiangchun updated YARN-9955:
--------------------------------
    Attachment: e04cffec-d7d9-4817-a483-4b0c6d8001f5-1092898.jpg
                9f6ef9ac-7b25-4aa0-a6db-f03b0bf003e0-1092898.jpg

> LogAggregationService Thread OOM
> --------------------------------
>
>                 Key: YARN-9955
>                 URL: https://issues.apache.org/jira/browse/YARN-9955
>             Project: Hadoop YARN
>          Issue Type: Bug
>    Affects Versions: 2.7.2, 2.7.3
>            Reporter: wangxiangchun
>            Priority: Major
>         Attachments: 9f6ef9ac-7b25-4aa0-a6db-f03b0bf003e0-1092898.jpg, e04cffec-d7d9-4817-a483-4b0c6d8001f5-1092898.jpg
>
>
> Because of some IPC problem,we found that if our recover directory stores too much container information.When we restart nodemanager , it appears to error:
> _java.lang.OutOfMemoryError: Unable to create new native thread_ 
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org