...
This includes making JobManager's memory-related metrics available in the UI. Additionally, the configuration parameters should be exposed similar to the TaskManager's overview (see FLIP-102: Add More Metrics to TaskManager).
JVM | Flink Compose0 | user conf key1 | configuration key2 | metric max3 | metric used3 |
Heap |
Heap | memoryConfiguration.frameworkHeap | Status.JVM.Memory.Heap.Max | Status.JVM.Memory.Heap.Used | |
Off-Heap |
Off-Heap | jobmanager.memory.off-heap.size | memoryConfiguration.frameworkOffHeap | Status.JVM.Memory.NonHeap.Max | Status.JVM.Memory.NonHeap.Used | ||||||||||||||||
JVM MetaSpace | memoryConfiguration.jvmMetaspace | Status.JVM.Memory.Metaspace.Max | Status.JVM.Memory.Metaspace.Used
| |||||||||||||||||
JVM Overhead | memoryConfiguration.jvmOverhead | Status.JVM.Memory.NonHeap.Max - Status.JVM.Memory.Metaspace.Max | Status.JVM.Memory.NonHeap.Used - Status.JVM.Memory.Metaspace.Used | |||||||||||||||||
0 The partitioning how it is described in org.apache.flink.runtime.clusterframework.TaskExecutorProcessSpec.
1 These are the configuration parameters used in the Flink configuration.
2 These are the Json paths to address the properties in the HTTP REST API response. Additionally, memoryConfiguration.totalFlinkMemory
and totalProcessMemory
are exposed through the REST API.
3 The metrics which are exposed through the metrics endpoint.
...