[
https://issues.apache.org/jira/browse/FLINK-15911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Till Rohrmann closed FLINK-15911.
---------------------------------
Resolution: Fixed
Fixed via
03b6e763d5578c3b503246a2a40e5fd1fb990570
8a1dbcc07d6b4ed7702741cd8b1c73d95f0d2583
3c997796e3aa6c4498849bcb029ffe6f5db515fc
9dc7a4a47f85153b98e1f50eb8917dd6c8e15c85
5c35d9d95144593193244a07b965e310707488a9
> 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
> Assignee: Xintong Song
> Priority: Blocker
> Labels: pull-request-available, usability
> Fix For: 1.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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)
