You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Andrey Zagrebin (Jira)" <ji...@apache.org> on 2020/04/27 07:19:00 UTC
[jira] [Closed] (FLINK-16745) Use JobManagerProcessUtils to start
JM container and pass JVM memory args
[ https://issues.apache.org/jira/browse/FLINK-16745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Zagrebin closed FLINK-16745.
-----------------------------------
Resolution: Done
merged into master by c3f0ad5ce297a9a22d226e45294a29ada28ce70a and 6c6e91d2da527915b96c1db86ecb4900448c4ef5
> Use JobManagerProcessUtils to start JM container and pass JVM memory args
> -------------------------------------------------------------------------
>
> Key: FLINK-16745
> URL: https://issues.apache.org/jira/browse/FLINK-16745
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes, Deployment / Mesos, Deployment / YARN, Runtime / Configuration, Runtime / Coordination
> Reporter: Andrey Zagrebin
> Assignee: Andrey Zagrebin
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.11.0
>
>
> JobManagerProcessUtils#processSpecFromConfig should be used to get JobManagerProcessSpec. Then JobManagerProcessSpec can be passed to ProcessMemoryUtils#generateJvmParametersStr to get JVM memory arg list string.
> The configuration should be fixed to fallback to JobManagerOptions.TOTAL_PROCESS_MEMORY if a legacy option is set (JobManagerProcessUtils#getConfigurationWithLegacyHeapSizeMappedToNewConfigOption) before passing it to JobManagerProcessUtils#processSpecFromConfig.
> Then the JVM memory arg list can be used to start the JM container in Yarn/Kubernetes active RMs instead of using the existing legacy heap options: `_jobmanager.heap.size_` (or `_jobmanager.heap.mb_`) and container cut-off options: `_containerized.heap-cutoff-ratio_` and `_containerized.heap-cutoff-min_`.
> Remove container cut-off options: `_containerized.heap-cutoff-ratio_` and `_containerized.heap-cutoff-min_`
--
This message was sent by Atlassian Jira
(v8.3.4#803005)