I filed a bug for this issue in our bug tracker https://issues.apache.org/jira/browse/FLINK-2821 (even though we can not do much about it, we should track the resolution of the issue).
On Mon, Oct 5, 2015 at 5:34 AM, Stephan Ewen <se...@apache.org> wrote: > I think this is yet another problem caused by Akka's overly strict message > routing. > > An actor system bound to a certain URL can only receive messages that are > sent to that exact URL. All other messages are dropped. > > This has many problems: > > - 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) > > Since this is inherent in Akka, I am puzzled what we can do about that. > Just googled a bit, seems other systems that use Akka (like Spark) have > stumbled across that issue as well... > > A good point to ask would be the akka mailing list. I can did into this > after the next release (2 weeks or so), if you want to help us speed this > up, you could ping the Akka mailing list as well. > > Greetings, > Stephan > > > > > On Sun, Oct 4, 2015 at 7:21 AM, Henry Saputra <henry.sapu...@gmail.com> > wrote: > >> Hi Emmanuel, >> >> Could you tell a bit how the proxy being setup? >> >> - Henry >> >> On Fri, Oct 2, 2015 at 1:55 PM, Emmanuel <ele...@msn.com> wrote: >> > When trying to access the JM through a proxy I get: >> > >> > >> > 19:26:23,113 ERROR akka.remote.EndpointWriter >> > - dropping message [class akka.actor.ActorSelectionMessage] for >> non-local >> > recipient [Actor[akka.tcp://flink@10.155.241.168:6123/]] arriving at >> > [akka.tcp://flink@10.155.241.168:6123] inbound addresses are >> > [akka.tcp://flink@10.152.1.107:6123] >> > >> > Is there a way to allow this look up through a proxy? >> > >> > Thanks >> > >> > >> > >
