[
https://issues.apache.org/jira/browse/FLINK-29572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17618373#comment-17618373
]
Xintong Song commented on FLINK-29572:
--------------------------------------
[~gzkevinl],
I'm still not entirely sure whether this is a valid requirement. Could you
explain a bit more about your use case:
1. Why do you need the TMs to run behind a proxy?
2. How does skipping the loopback address help in this case? Do you mean JM /
RM can connect to the TM via its hostname / ip-address? If yes, then it come
back to question 1).
3. Can this issue be resolved by setting the proxy to reject the loopback
interface?
> 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)
