You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (JIRA)" <ji...@apache.org> on 2019/05/28 07:18:00 UTC
[jira] [Closed] (FLINK-10884) Flink on yarn TM container will be
killed by nodemanager because of the exceeded physical memory.
[ https://issues.apache.org/jira/browse/FLINK-10884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Yao closed FLINK-10884.
----------------------------
Resolution: Won't Fix
See https://github.com/apache/flink/pull/7185#issuecomment-447890879
> Flink on yarn TM container will be killed by nodemanager because of the exceeded physical memory.
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-10884
> URL: https://issues.apache.org/jira/browse/FLINK-10884
> Project: Flink
> Issue Type: Bug
> Components: Deployment / YARN, Runtime / Coordination
> Affects Versions: 1.5.5, 1.6.2, 1.7.0
> Environment: version : 1.6.2
> module : flink on yarn
> centos jdk1.8
> hadoop 2.7
> Reporter: wgcn
> Assignee: wgcn
> Priority: Major
> Labels: pull-request-available, yarn
> Time Spent: 10m
> Remaining Estimate: 0h
>
> TM container will be killed by nodemanager because of the exceeded physical memory. I found the lanuch context lanuching TM container that "container memory = heap memory + offHeapSizeMB" at the class org.apache.flink.runtime.clusterframework.ContaineredTaskManagerParameters from line 160 to 166 I set a safety margin for the whole memory container using. For example if the container limit 3g memory, the sum memory that "heap memory + offHeapSizeMB" is equal to 2.4g to prevent the container being killed. Do we have the ready-made solution or I can commit my solution.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)