THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
| Flink Memory Model | Flink configuration1 | Effective Configuration REST API2 | Metric3 | Used key | Total key | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Heap | jobmanager.memory.heap.size | ???jobmanager.memory.heap.size | Status.JVM.Memory.Heap | Used | Max | ||||||||
| Off-Heap | jobmanager.memory.off-heap.size | ???jobmanager.memory.off-heap.size | - | - | - | ||||||||
| JVM Metaspace | jobmanager.memory.jvm-metaspace.size | ???jobmanager.memory.jvm-metaspace.size | Status.JVM.Memory.Metaspace | Used | Max | ||||||||
| JVM Overhead | jobmanager.memory.jvm-overhead.min | ???jobmanager.memory.jvm-overhead.min/ jobmanager.memory.jvm-overhead.max4 | - | - | - | ||||||||
jobmanager.memory.jvm-overhead.max |
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 responseconfig parameters exposed through the cluster config REST API. Their names matching the actual Flink config as the effective configuration is generated out of the passed configuration. Jira server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-19662
3 The metrics which are exposed through the JobManager's metrics REST API.
4 min and max are having the same value.
Frontend Design
Display metrics inside JVM, outside JVM and GC
...