[ https://issues.apache.org/jira/browse/FLINK-29572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17615420#comment-17615420 ]
Xintong Song commented on FLINK-29572: -------------------------------------- I think this was introduced by FLINK-24474. In FLINK-24474, we change the default bind address to the loopback address. However, when using loopback, the address reported to JM/RM should be different from the bind address. Thus, `ConnectionUtils#findAddressUsingStrategy` should return `InetAddress.getLocalHost()` in this case. [~chesnay], could you confirm this? > 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)