[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734537#comment-15734537
]
Philipp von dem Bussche commented on FLINK-2821:
------------------------------------------------
Thanks [~mxm] this is working for me now. I tested again and am purely using
Rancher DNS names now as well as can deploy my jobs from my build service.
There are two things I still had to do which was a) to also update the flink
version on my build slave so it seems the client also got some changes and b)
to exactly match the hostname when connecting e.g. from the client. So in
Rancher a host can be reached by hostname.stackname where in my case stackname
was in camel case and then I also had to use camel case to connect from the
client to the jobmanager because otherwise the jobmanager would again refuse.
Anyways this looks quite good now and I will test further with this. Thanks
again for the help !
> 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)
