You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2019/09/09 15:35:00 UTC
[jira] [Commented] (FLINK-13445) Distinguishing Memory
Configuration for TaskManager and JobManager
[ https://issues.apache.org/jira/browse/FLINK-13445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16925783#comment-16925783 ]
Stephan Ewen commented on FLINK-13445:
--------------------------------------
Hi David! Flink 1.10 will not have the {{heap-cutoff}} parameters any more.
You can check this design proposal for the details:
https://cwiki.apache.org/confluence/display/FLINK/FLIP-49%3A+Unified+Memory+Configuration+for+TaskExecutors
> 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)