[ 
https://issues.apache.org/jira/browse/FLINK-16745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Andrey Zagrebin updated FLINK-16745:
------------------------------------
    Description: 
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/Mesos/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_`.

  was:
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/Mesos/Kubernetes active RMs instead of using the existing legacy heap 
options: `_jobmanager.heap.size_` (or `_jobmanager.heap.mb_`).


> 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
>            Priority: Major
>             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/Mesos/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_`.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to