[jira] [Created] (FLINK-16751) Expose bind port for Flink metric query service

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Created] (FLINK-16751) Expose bind port for Flink metric query service

Shang Yuanchun (Jira)
Till Rohrmann created FLINK-16751:
-------------------------------------

             Summary: Expose bind port for Flink metric query service
                 Key: FLINK-16751
                 URL: https://issues.apache.org/jira/browse/FLINK-16751
             Project: Flink
          Issue Type: Improvement
          Components: Runtime / Coordination
    Affects Versions: 1.11.0
            Reporter: Till Rohrmann
             Fix For: 1.11.0


With FLINK-15911 it is now possible to run Flink behind a NAT/with an unresolvable external address. However, due to FLINK-11127, the {{MetricFetcherImpl}} tries to connect to the {{TaskManagers}} instead of the other way around. If the TM is running behind a NAT, it would require to define an external port. At the moment, it is only possible to configure the bind port via {{metrics.internal.query-service.port}}.

I think in order to properly solve this problem we either solve FLINK-11127 or we introduce a {{metrics.internal.query-service.bind-port}} option which allows to configure a bind port. With such an option, {{metrics.internal.query-service.port}} would become the external port.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)