flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philipp von dem Bussche (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-2821) Change Akka configuration to allow accessing actors from different URLs
Date Thu, 20 Oct 2016 16:57:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15592357#comment-15592357

Philipp von dem Bussche commented on FLINK-2821:

Thank you for all your effort [~mxm]. I have tested this and was able to connect a jobmanager
and a task manager in a docker-machine environment on my Mac as well as in Rancher. For the
Rancher setup to work though I had to have the bind-address be set to . I think this
makes sense since Rancher introduces this additional 10.x address (on top of the 172.x address
given by Docker) but when specifying the hostname as bind address it would only bind to the
172.x address.
One other thing which I realized was that my local flink cli on my Mac would not work together
with your customer build anymore because of version discrepancies. I felt this is quite harsh
given that I am running 1.1.3 on bother sides but obviously different builds.
I will play around with this a bit more and send some data across and let you know if I see
anything else popping up.
Thanks again !

> 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 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

View raw message