flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chesnay Schepler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-9543) Expose JobMaster IDs to metric system
Date Wed, 04 Jul 2018 12:50:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-9543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16532714#comment-16532714

Chesnay Schepler commented on FLINK-9543:

Moving this issue to 1.7, on the assumption that we're dropping legacy mode in that release.

Exposing the JobManager (and Dispatcher) ID _properly _is at the moment not trivial since
we still support the legacy mode, with significant parts of the metric system being shared
between them. The risk for inconsistencies or subtle issues is to big for me to comfortable
include this in 1.6.

I'm unblocking FLINK-9187 from this issue.

> Expose JobMaster IDs to metric system
> -------------------------------------
>                 Key: FLINK-9543
>                 URL: https://issues.apache.org/jira/browse/FLINK-9543
>             Project: Flink
>          Issue Type: New Feature
>          Components: Local Runtime, Metrics
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
> To be able to differentiate between metrics from different taskmanagers we should expose
the Jobmanager ID (i.e. the resourceID) to the metric system, like we do for TaskManagers.

This message was sent by Atlassian JIRA

View raw message