[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15731314#comment-15731314
]
Philipp von dem Bussche commented on FLINK-2821:
------------------------------------------------
Hello [~mxm], some more feedback on my testing back in the Rancher environment.
The connection between TaskManager and JobManager via the Rancher DNS name is
working now, however I still seem to have a slight problem deploying my Jobs.
I am doing this from Jenkins using the flink cli and running it with a hostname
(It is still slightly different to what I have configured on the JobManager)
seems to trigger an IP resolution and then it is trying to connect via IP
rather than hostname and hence the cli is still blocked from connecting on the
JobManager side.
Can we make it somehow that hostname and whatever this resolves to on the
JobManager is allowed to connect ?
Output from flink cli command:
flink list --jobmanager flink-jobmanager.analyticsstack:6123
Retrieving JobManager.
Using address /10.42.202.225:6123 to connect to JobManager.
------------------------------------------------------------
The program finished with the following exception:
org.apache.flink.runtime.leaderretrieval.LeaderRetrievalException: Could not
retrieve the leader gateway
at
org.apache.flink.runtime.util.LeaderRetrievalUtils.retrieveLeaderGateway(LeaderRetrievalUtils.java:127)
Output from jobamanager logfile:
2016-12-08 06:39:27,581 ERROR akka.remote.EndpointWriter
- dropping message [class akka.actor.ActorSelectionMessage] for
non-local recipient [Actor[akka.tcp://flink@10.42.202.225:6123/]] arriving at
[akka.tcp://flink@10.42.202.225:6123] inbound addresses are
[akka.tcp://flink@flink-jobmanager:6123]
2016-12-08 06:39:37,711 WARN akka.remote.ReliableDeliverySupervisor
- Association with remote system
[akka.tcp://flink@172.17.0.6:46589] has failed, address is now gated for [5000]
ms. Reason: [Disassociated]
> 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)
