[ 
https://issues.apache.org/jira/browse/FLINK-29572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17624813#comment-17624813
 ] 

Xintong Song commented on FLINK-29572:
--------------------------------------

bq. If this works, TM will report its address as 127.0.0.1:6223. JM can RPC 
this address as well. But as soon as you have multiple TMs, all of them will 
report their address as 127.0.0.1:6223. Obviously only one will succeed.

You said that it would work if there's only one TM using a 127.0.0.1 address. 
Then I don't understand why it couldn't work with multiple TMs using the same 
address but different ports. A {{TaskManagerLocation}} is uniquely by its 
address *and* port. Having multiple TMs using the same IP address with 
different ports should not confuse JM.

> 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)

Reply via email to