[FLINK-16745] Use JobManagerProcessUtils to start JM container and pass JVM memory args

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.11.0
• Component/s: Deployment / Kubernetes, Deployment / Mesos, Deployment / YARN, Runtime / Configuration, Runtime / Coordination
• Labels: pull-request-available
• Assignee: Andrey Zagrebin
• Reporter: Andrey Zagrebin
• Created: 24/Mar/20 08:22
• Updated: 27/Apr/20 07:18
• Resolved: 27/Apr/20 07:18

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/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`

Issue Links

• blocks: FLINK-16746 Deprecate legacy heap memory option for JM and expose the new ones in docs
• is blocked by: FLINK-16615 Introduce data structures and utilities to calculate Job Manager memory components
• links to: GitHub Pull Request #11675
• links to: GitHub Pull Request #11675