[FLINK-29572] Flink Task Manager skip loopback interface for resource manager registration

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.15.3
• Component/s: API / Core

Environment

Flink 1.15.2

Kubernetes with Istio Proxy

• Assignee: Unassigned
• Reporter: Kevin Li
• Created: 10/Oct/22 16:56
• Updated: 17/Nov/22 10:04
• Resolved: 17/Nov/22 10:04

Description

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.

 

Issue Links

• duplicates: FLINK-27341 TaskManager running together with JobManager are bind to 127.0.0.1
• is caused by: FLINK-24474 Standalone clusters should bind to localhost by default