THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Page properties | ||
|---|---|---|
|
Table of Contents
Status
Current state: "Under Discussion"
...
...
...
|
...
...
|
Released:Table of Contents
Motivation
This FLIP suggests aligning the memory model and configuration for Job Manager (JM) with the recently introduced memory model of Task Manager (TM) in FLIP-49 .
...
Memory component | options | Default value |
Total Process Memory | jobmanager.memory.process.size | None (“1472m” in default flink-conf.yaml ) |
Total Flink Memory | jobmanager.memory.flink.size | None |
JVM Heap | jobmanager.memory.heap.size | None |
Off-heap memory | jobmanager.memory.off-heap.size | “128m” |
JVM Metaspace | jobmanager.memory.jvm-metaspace.size | “256m” |
JVM Overhead | jobmanager.memory.jvm-overhead.min | “192m” |
jobmanager.memory.jvm-overhead.max | “1g” | |
jobmanager.memory.jvm-overhead.fraction “192m” “1g” | 0.1 |
Implementation Steps
- Introduced new options
- Introduce data structures and utilities
- Data structure to store memory sizes of JM
- Utility for calculating memory sizes from configuration
- Extend the calculation utility and BashJavaUtils with generating JVM arguments to start JM process
- Call BashJavaUtils in the standalone startup scripts and use returned JVM arguments to start JM JVM process (ClusterEntryPoint) instead of current bash code
- Use new memory calculation utility to get the Total Process Memory size and the JVM arguments to start the JM container (ClusterEntryPoint) in the containerized environment
...