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 Mon, 05 Dec 2016 20:19:59 GMT

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

Philipp von dem Bussche commented on FLINK-2821:

Hi [~mxm], I wanted to give this a try but I am not sure if I am testing this correctly.
Do I just have to set jobmanager.rpc.address but to the hostname that will be used for access
from outside ?
I tried to use a name that is not resolvable on the host itself and that fails but this is
on my local docker environment and this should be different as soon as I move this to rancher.

> 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