[
https://issues.apache.org/jira/browse/FLINK-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925917#comment-16925917
]
Till Rohrmann commented on FLINK-13445:
---------------------------------------
I think Flip-49 does not really address the memory configuration of the cluster
entrypoint process because it concentrates on the {{TaskExecutor}} process. So
either we say that the existing cluster wide configuration settings will then
apply only to the cluster entrypoin/application master or it might still make
sense to add explicit configuration settings. Ideally, we would do this as part
of overhaul of the cluster entrypoint/application master process setup similar
to Flip-49.
> Distinguishing Memory Configuration for TaskManager and JobManager
> ------------------------------------------------------------------
>
> Key: FLINK-13445
> URL: https://issues.apache.org/jira/browse/FLINK-13445
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Configuration
> Affects Versions: 1.8.1
> Reporter: madong
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> we use flink to run some job build in non-java language, so we increase the
> value of `containerized.heap-cutoff-ratio` to reserve more memory for
> non-java process , which would affect memory allocation for jobManager.
> Considering the different behaviors of taskManager and jobManager, should we
> use this configuration separately？
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
