You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/02/05 09:29:00 UTC

[jira] [Updated] (FLINK-15911) Flink does not work over NAT

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

Stephan Ewen updated FLINK-15911:
---------------------------------
    Priority: Blocker  (was: Major)

> Flink does not work over NAT
> ----------------------------
>
>                 Key: FLINK-15911
>                 URL: https://issues.apache.org/jira/browse/FLINK-15911
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.10.0
>            Reporter: Till Rohrmann
>            Priority: Blocker
>              Labels: usability
>             Fix For: 1.11.0
>
>
> Currently, it is not possible to run Flink over network address translation. The problem is that the Flink processes do not allow to specify separate bind and external ports. Moreover, the {{TaskManager}} tries to resolve the given {{taskmanager.host}} which might not be resolvable. This breaks NAT or docker setups where the external address is not resolvable from within the container/internal network.



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