You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2020/02/19 14:46:00 UTC

[jira] [Updated] (FLINK-15948) Resource will be wasted when the task manager memory is not a multiple of Yarn minimum allocation

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

Till Rohrmann updated FLINK-15948:
----------------------------------
    Issue Type: Improvement  (was: Bug)

> Resource will be wasted when the task manager memory is not a multiple of Yarn minimum allocation
> -------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-15948
>                 URL: https://issues.apache.org/jira/browse/FLINK-15948
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / YARN
>    Affects Versions: 1.10.0
>            Reporter: Yang Wang
>            Priority: Minor
>
> If the {{taskmanager.memory.process.size}} is set to 2000m and the Yarn minimum allocation is 128m, we will get a container with 2048m. Currently, {{TaskExecutorProcessSpec}} is built with 2000m, so we will have 48m wasted and they could not be used by Flink.
> I think Flink has accounted all the jvm heap, off-heap, overhead resources. So we should not leave these free memory there. And i suggest to update the {{TaskExecutorProcessSpec}} according to the Yarn allocated container.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)