You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2019/12/23 02:08:00 UTC
[jira] [Commented] (FLINK-15356) Add applicationId to existing
flink metrics running on yarn
[ https://issues.apache.org/jira/browse/FLINK-15356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002056#comment-17002056 ]
Yang Wang commented on FLINK-15356:
-----------------------------------
I do not think adding the applicationId is a common fix. When we run flink cluster on kubernetes/mesos, we will not have applicationId.
I'm not sure whether the clusterId exists in the metrics. It is a common unique identifier for each flink cluster.
> Add applicationId to existing flink metrics running on yarn
> -----------------------------------------------------------
>
> Key: FLINK-15356
> URL: https://issues.apache.org/jira/browse/FLINK-15356
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Forward Xu
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When sending metrics to Prometheus, these systems have only the Flink job ID, and the Flink job ID is UUID, which cannot be associated with the application job on the yarn. Therefore, we need to increase the applicationId when running on yarn. This helps us to accurately find the corresponding job on yarn when the metric is abnormal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)