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

Posted to yarn-dev@hadoop.apache.org by "Xianghao Lu (JIRA)" <ji...@apache.org> on 2018/08/01 12:00:00 UTC

[jira] [Created] (YARN-8609) NM oom because of large container statuses

Xianghao Lu created YARN-8609:
---------------------------------

             Summary: NM oom because of large container statuses
                 Key: YARN-8609
                 URL: https://issues.apache.org/jira/browse/YARN-8609
             Project: Hadoop YARN
          Issue Type: Bug
          Components: nodemanager
            Reporter: Xianghao Lu


Sometimes, NodeManger will send large container statuses to ResourceManager when NodeManger recovering, as a result , NodeManger will be failed to start because of oom.
In my case, the large container statuses size is 135M, which contain 11 container statuses, and I find the diagnostics of 5 container is very large(27M), so, I truncate the container diagnostics as the patch.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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