[
https://issues.apache.org/jira/browse/YARN-8609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16571033#comment-16571033
]
Xianghao Lu edited comment on YARN-8609 at 8/7/18 2:36 AM:
-----------------------------------------------------------
Thank you for your patience!
I know what you say, and my hadoop version is 2.7.2 which don't contain the
change in YARN-3998. Indeed, it would not take up too much memory if running
with -YARN-3998.-
However, for example, if the raw diagnostic is largeExceptionMessage +
fixedString + fixedString + ... , all meaningful fixedString will be discarded
when running with YARN-3998. So, if we do truncation in for loop, all kinds of
diagnostic info will retain. This is what I want to say and it is a small
improvement.
Besides, diagnosticsMaxSize in -YARN-3998- is also necessary, and, there is a
small possibility to reach diagnosticsMaxSize with appropriate truncation in
for loop.
was (Author: luxianghao):
Thank you for your patience!
I know what you say, and my hadoop version is 2.7.2 which don't contain the
change in YARN-3998. Indeed, it would not take up too much memory if running
with -YARN-3998.-
However, for example, if the raw diagnostic is largeExceptionMessage +
fixedString + fixedString + ... , all meaningful fixedString will be discarded
when running with YARN-3998. So, if we do truncation in for loop, all kinds of
diagnostic info will retain. This is what I want to say and it is a small
improvement.
> 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
> Priority: Major
> Attachments: YARN-8609.001.patch, contain_status.jpg, oom.jpeg
>
>
> Sometimes, NodeManger will send large container statuses to ResourceManager
> when NodeManger start with 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 containers are 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
