[
https://issues.apache.org/jira/browse/FLINK-16751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16751:
-----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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, Runtime / Metrics
> Affects Versions: 1.11.0
> Reporter: Till Rohrmann
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
