[
https://issues.apache.org/jira/browse/FLINK-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894686#comment-16894686
]
Stephan Ewen commented on FLINK-13445:
--------------------------------------
I am thinking of proposing a FLIP for 1.10 to rethink the whole memory
configuration a bit and make it easier.
Can you share what problem you are trying to solve here?
> 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
>
> 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
(v7.6.14#76016)
