[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15737849#comment-15737849
]
Philipp von dem Bussche commented on FLINK-2821:
------------------------------------------------
Just looking into another use case where communication with the jobmanager is
required but where the client is actually not part of the Rancher or Docker
environment. So for that I would not use the hostname specified as rpc address,
well I could not. This is a use case I am seeing when deploying the jobmanager
lets say to AWS but I want to deploy the jobs from my on prem build system. The
jobmanager (container) has a name that is resolveable from the Internet but
since it is also part of the Rancher network I have it listen on the Rancher
DNS name. This makes sense so that JobManager and TaskManager will only
communicate within the Rancher network but still I have to from outside deploy
the jobs and would do that via the Internet host name. However I would then
have the JobManager registered to the Internet host name and subsequently the
taskmanager would also have to use that name.
So for this now to work I would need the JobManager to accept communications on
at least two rpc addresses. I still don't quite understand why this is being
verified anyways, why not just serve any connection as long as it hits the
right port ?
> Change Akka configuration to allow accessing actors from different URLs
> -----------------------------------------------------------------------
>
> Key: FLINK-2821
> URL: https://issues.apache.org/jira/browse/FLINK-2821
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Reporter: Robert Metzger
> Assignee: Maximilian Michels
>
> Akka expects the actor's URL to be exactly matching.
> As pointed out here, cases where users were complaining about this:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Error-trying-to-access-JM-through-proxy-td3018.html
> - Proxy routing (as described here, send to the proxy URL, receiver
> recognizes only original URL)
> - Using hostname / IP interchangeably does not work (we solved this by
> always putting IP addresses into URLs, never hostnames)
> - Binding to multiple interfaces (any local 0.0.0.0) does not work. Still
> no solution to that (but seems not too much of a restriction)
> I am aware that this is not possible due to Akka, so it is actually not a
> Flink bug. But I think we should track the resolution of the issue here
> anyways because its affecting our user's satisfaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
