[FLINK-16742] Extend and use BashJavaUtils to start JM JVM process and pass JVM memory args

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Done
• Fix Version/s: 1.11.0
• Component/s: Deployment / Scripts, Runtime / Configuration, Runtime / Coordination
• Labels: pull-request-available
• Assignee: Xintong Song
• Reporter: Andrey Zagrebin
• Created: 24/Mar/20 08:05
• Updated: 13/May/20 07:50
• Resolved: 27/Apr/20 07:16

Description

Currently, the legacy options `jobmanager.heap.size` (or `jobmanager.heap.mb`) is used in JM standalone bash scripts to pass JVM heap size arg and start JM JVM process.

BashJavaUtils should be extended to get JVM memory arg list string from Flink configuration. BashJavaUtils can use JobManagerProcessUtils#processSpecFromConfig to obtain JobManagerProcessSpec. JobManagerProcessSpec can be passed to ProcessMemoryUtils#generateJvmParametersStr to get JVM memory arg list string.

The configuration should be fixed to fallback to JobManagerOptions.JVM_HEAP_MEMORY if a legacy option is set (JobManagerProcessUtils#getConfigurationWithLegacyHeapSizeMappedToNewConfigOption) before passing it to JobManagerProcessUtils#processSpecFromConfig.

Then the JVM memory arg list from BashJavaUtils can be used in JM standalone bash scripts instead the existing bash code which parses legacy heap options: `jobmanager.heap.size` (or `jobmanager.heap.mb`).

Issue Links

• blocks: FLINK-16746 Deprecate legacy heap memory option for JM and expose the new ones in docs
• causes: FLINK-17652 Legacy JM heap options should fallback to new JVM_HEAP_MEMORY in standalone
• is blocked by: FLINK-16615 Introduce data structures and utilities to calculate Job Manager memory components
• links to: GitHub Pull Request #11545