[
https://issues.apache.org/jira/browse/FLINK-29572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626342#comment-17626342
]
Xintong Song commented on FLINK-29572:
--------------------------------------
I'm still not convinced that this is a bug of Flink. Maybe we can live with the
disagreement for now and focus solving your problem first.
bq. You don't have to configure different ports for each task manager. You just
need to remove `taskmanager.rpc.port` from your configuration, and Flink by
default should use random ports.
Have you tried the random port approach?
One more question: when not binding to the loopback address, does all the
traffics still go through the proxy?
> Flink Task Manager skip loopback interface for resource manager registration
> ----------------------------------------------------------------------------
>
> Key: FLINK-29572
> URL: https://issues.apache.org/jira/browse/FLINK-29572
> Project: Flink
> Issue Type: Bug
> Components: API / Core
> Affects Versions: 1.15.2
> Environment: Flink 1.15.2
> Kubernetes with Istio Proxy
> Reporter: Kevin Li
> Priority: Major
>
> Currently Flink Task Manager use different local interface to bind to connect
> to Resource Manager. First one is Loopback interface. Normally if Job Manager
> is running on remote host/container, using loopback interface to connect will
> fail and it will pick up correct IP address.
> However, if Task Manager is running with some proxy, loopback interface can
> connect to remote host as well. This will result 127.0.0.1 reported to
> Resource Manager during registration, even Job Manager/Resource Manager runs
> on remote host, and problem will happen. For us, only one Task Manager can
> register in this case.
> I suggest adding configuration to skip Loopback interface check if we know
> Job/Resource Manager is running on remote host/container.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
