You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/11/21 10:40:00 UTC

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

     [ 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 stale-minor  (was: auto-deprioritized-major)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-major, stale-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)