[
https://issues.apache.org/jira/browse/FLINK-10276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328570#comment-17328570
]
Flink Jira Bot commented on FLINK-10276:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Job Manager and Task Manager Metrics Reporter Ports Configuration
> -----------------------------------------------------------------
>
> Key: FLINK-10276
> URL: https://issues.apache.org/jira/browse/FLINK-10276
> Project: Flink
> Issue Type: New Feature
> Components: Runtime / Configuration, Runtime / Metrics
> Reporter: Deirdre Kong
> Priority: Major
> Labels: stale-major, starter
>
> *Problem Statement:*
> When deploying Flink using YARN, the job manager and task manager can be on
> the same node or different nodes. Say I specify the port range to be
> 9249-9250, if JM and TM are deployed on the same node, the port for JM will
> be 9249 and the port for TM will be 9250. If JM and TM are deployed on
> different nodes, then the ports for JM and TM will be 9249.
> I can only configure Prometheus once for the ports to scrape JM and TMs
> metrics. In this case, I won't know whether port 9249 is for JM or TM. If
> would be great if we can specify in flink-conf.yaml on the port we want for
> JM reporter and TMs reporter.
> *Comment from Till:*
> I think we could extend Vino's proposal for Yarn as well: Maybe it makes
> sense to allow to override certain configuration settings for the
> TaskManagers when deploying on Yarn. That way one could define a fixed port
> for the JM and a port range for the TMs. Having such a distinction you can
> configure your Prometheus to scrape for the single JM and the TMs
> individually. However, Flink does not yet support such a feature. You can
> open a JIRA issue to track the problem.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
