[
https://issues.apache.org/jira/browse/FLINK-15911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17306173#comment-17306173
]
Bo Cui edited comment on FLINK-15911 at 3/22/21, 12:51 PM:
-----------------------------------------------------------
!screenshot-1.png!
!screenshot-2.png!
i think it might be better on yarn...taskExecutorHostname must be resolved
{quote}I'm not sure if the application should decide which network interface on
the machine should be used.
{quote}
TM use the IP address assigned by the JM.
was (Author: bo cui):
!screenshot-1.png!
!screenshot-2.png!
i think it might be better on yarn...taskExecutorHostname must be resolved
{quote}I'm not sure if the application should decide which network interface on
the machine should be used.
{quote}
TM use the IP address assigned to the JM.
> 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
>
> Attachments: screenshot-1.png, screenshot-2.png
>
> 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)
