You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Xintong Song (Jira)" <ji...@apache.org> on 2022/10/28 02:16:00 UTC
[jira] [Comment Edited] (FLINK-29572) Flink Task Manager skip loopback interface for resource manager registration
[ https://issues.apache.org/jira/browse/FLINK-29572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17625383#comment-17625383 ]
Xintong Song edited comment on FLINK-29572 at 10/28/22 2:15 AM:
----------------------------------------------------------------
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.
IMHO, allowing components from different hosts to bi-directionally communicate with each other via the loopback address does not sounds like a common use case. It seems to be a violation of the loopback address semantics. This is probably more a problem of the proxy software, rather than Flink.
I'd love to help you find a workaround to get things work if possible. However, as one of the maintainers of the Flink project, I'd be negative to introduce such a knob for such an unusual use case.
was (Author: xintongsong):
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.
IMHO, allowing components from different hosts to bi-directionally communicate with each other via the loopback address does not sounds like a common use case. It seems to be a violation of the loopback address semantics. This is probably more a problem of the proxy software, rather than Flink.
I'd love to help you find a workaround to get things work. However, as one of the maintainers of the Flink project, I'd be negative to introduce such a knob for such an unusual use case.
> 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)