[
https://issues.apache.org/jira/browse/FLINK-15948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035175#comment-17035175
]
Yang Wang commented on FLINK-15948:
-----------------------------------
# Yes. What i mean is to check the yarn min allocation at client side.
# Of course it could get the container size from Yarn/K8s. However, from the
user's perspective, they are convenient to know how many resources the Flink
cluster is consuming. Since they could not find it in the Flink dashboard or
rest api.
> 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: Bug
> Components: Deployment / YARN
> Affects Versions: 1.10.0
> Reporter: Yang Wang
> Priority: Major
>
> 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)
