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 "Tapas Sen (JIRA)" <ji...@apache.org> on 2018/06/13 09:37:00 UTC
[jira] [Updated] (YARN-8425) Yarn container getting killed due to
running beyond physical memory limits
[ https://issues.apache.org/jira/browse/YARN-8425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tapas Sen updated YARN-8425:
----------------------------
Summary: Yarn container getting killed due to running beyond physical memory limits (was: Yarn container getting due to running beyond physical memory limits)
> Yarn container getting killed due to running beyond physical memory limits
> --------------------------------------------------------------------------
>
> Key: YARN-8425
> URL: https://issues.apache.org/jira/browse/YARN-8425
> Project: Hadoop YARN
> Issue Type: Task
> Components: applications, container-queuing, yarn
> Affects Versions: 2.7.6
> Reporter: Tapas Sen
> Priority: Major
> Attachments: yarn_configuration_1.PNG, yarn_configuration_2.PNG, yarn_configuration_3.PNG
>
>
> Hi,
> Getting these error.
>
> 2018-06-12 17:59:07,193 INFO [AsyncDispatcher event handler] org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics report from attempt_1527758146858_45040_m_000008_3: Container [pid=15498,containerID=container_e60_1527758146858_45040_01_000041] is running beyond physical memory limits. Current usage: 8.1 GB of 8 GB physical memory used; 12.2 GB of 16.8 GB virtual memory used. Killing container.
>
> Yarn resource configuration will in attachment.
>
> Any lead would be appreciated.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org