[FLINK-16751] Expose bind port for Flink metric query service

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.11.0
• Component/s: Runtime / Coordination, Runtime / Metrics
• Labels: auto-deprioritized-major auto-deprioritized-minor
• Assignee: Unassigned
• Reporter: Till Rohrmann
• Created: 24/Mar/20 14:21
• Updated: 29/Nov/21 10:39

Description

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 external and bind port at the same time via metrics.internal.query-service.port. Hence, the external port always needs to be the same as the bind port if port forwarding should work.

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.

Issue Links

• is related to: FLINK-15911 Flink does not work over NAT
• is related to: FLINK-11127 Make metrics query service establish connection to JobManager