[
https://issues.apache.org/jira/browse/FLINK-15911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17305915#comment-17305915
]
Bo Cui commented on FLINK-15911:
--------------------------------
1、 all client IP can access the port through any NIC. yes ,the problem can be
solved by using the firewall, but no network adapter is missing from the
firewall, and it is not a good practice to listen on all interfaces
2、like
https://github.com/apache/flink/blob/a33e6bd390a9935c3e25b6913bed0ff6b4a78818/flink-yarn/src/main/java/org/apache/flink/yarn/YarnTaskExecutorRunner.java#L140,
we can use taskmanager.host, or update value of taskmanager.bind-host in
YarnTaskExecutorRunner#setupConfigurationFromVariables.
thx
> 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)
