You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2016/01/13 11:27:40 UTC

[jira] [Closed] (FLINK-3151) YARN kills Flink TM containers due to memory overuse (outside heap/offheap)

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

Ufuk Celebi closed FLINK-3151.
------------------------------
       Resolution: Fixed
    Fix Version/s: 0.10.2
                   1.0.0

Fixed via 66dd32d (0.10) and d92e422 (1.0-SNAPSHOT).

> YARN kills Flink TM containers due to memory overuse (outside heap/offheap)
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-3151
>                 URL: https://issues.apache.org/jira/browse/FLINK-3151
>             Project: Flink
>          Issue Type: Bug
>          Components: TaskManager
>    Affects Versions: 1.0.0, 0.10.1
>         Environment: 48 cores
>            Reporter: Robert Metzger
>            Assignee: Ufuk Celebi
>            Priority: Blocker
>             Fix For: 1.0.0, 0.10.2
>
>
> A Flink user who's running Flink on YARN with 1 processing slot, 2 GB of TM memory on a machine with 48 reported CPU cores is running into issues with TM containers being killed due to memory overuse.
> Setting the YARN memory cutoff to 0.5 resolves the problem, but its not really a feasible approach.
> Another solution to the problem was downgrading netty again from 4.0.31.Final to 4.0.27.Final resolved the issue.
> We upgraded Netty between 0.9 and 0.10.
> Most likely netty changed its behavior between the releases.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)