flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (FLINK-9703) Mesos does not expose TM Prometheus port
Date Fri, 13 Jul 2018 12:41:00 GMT

     [ https://issues.apache.org/jira/browse/FLINK-9703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Till Rohrmann resolved FLINK-9703.
       Resolution: Fixed
    Fix Version/s: 1.6.0

Fixed via b74594c488e4c5428c5391b89c32ae6fd7d98a79

> Mesos does not expose TM Prometheus port
> ----------------------------------------
>                 Key: FLINK-9703
>                 URL: https://issues.apache.org/jira/browse/FLINK-9703
>             Project: Flink
>          Issue Type: Bug
>          Components: Mesos
>            Reporter: Rune Skou Larsen
>            Assignee: Rune Skou Larsen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.6.0
> LaunchableMesosWorker makes Mesos expose these ports for a Task Manager:
> {{private static final String[] TM_PORT_KEYS = {}}
> {{ "taskmanager.rpc.port",}}
> {{ "taskmanager.data.port"};}}
> But when running Prometheus Exporter on a TM, another port needs to be exposed to make Flink's Prometheos
endpoint externally scrapable by the Prometheus server. By default this is port 9249, but it
is configurable according to:
> [https://ci.apache.org/projects/flink/flink-docs-release-1.6/monitoring/metrics.html#prometheus-orgapacheflinkmetricsprometheusprometheusreporter]
> My plan is to make a PR, that just adds another config option for mesos, to enable custom
ports to be exposed in the provisioned TMs.
> I considered carrying parts of the Metrics config into the Mesos code to automatically map metrics
ports in mesos. But making such a "shortcut" between Flink's metrics and mesos modules would probably
need some sort of integration testing, so I prefer the simple solution of just adding another
Mesos config option. But comments are welcome.

This message was sent by Atlassian JIRA

View raw message