Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
1.4.0
Description
Currently, the TaskManager registers the TaskManagerMetricGroup under its InstanceID and thereby binding its metrics effectively to the lifetime of its registration with the JobManager. This has also implications how the REST handler retrieve the TaskManager metrics, namely by its InstanceID.
I would actually propose to register the TaskManagerMetricGroup under the TaskManager/TaskExecutor ResourceID which is valid over the whole lifetime of the TaskManager/TaskExecutor. That way we would also be able to query metrics independent of the connection status to the JobManager.
Attachments
Issue Links
- supercedes
-
FLINK-7100 TaskManager metrics are registered twice
- Resolved
- links to