THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
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 |
VM
Flink Compose | user conf key1 | configuration key2 | metric max3 | metric used |
3 |
| Heap |
Framework Heap | memoryConfiguration. |
frameworkHeap | Status.JVM.Memory.Heap.Max | Status.JVM.Memory.Heap.Used |
Off-Heap |
| Framework 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 |
jobmanager.memory.jvm-overhead.max
other
-
-
Outside JVM
Mapped
-
-
-
| ||||||||
JVM Overhead | memoryConfiguration.jvmOverhead | Status.JVM.Memory. |
Direct
-
jobmanager.memory.off-heap.size
NonHeap.Max - Status.JVM.Memory.Metaspace.Max | Status.JVM.Memory.NonHeap. |
Used - Status.JVM.Memory. |
Metaspace.Used |
Native
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.
Frontend Design
Display metrics inside JVM, outside JVM and GC
...