[
https://issues.apache.org/jira/browse/FLINK-1559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-1559.
---------------------------------
Resolution: Fixed
Fixed via 2dcff4c122f37ca58a485e886fec9295fef0c832
> Normalize all Akka URLs to use IP addresses, not hostnames
> ----------------------------------------------------------
>
> Key: FLINK-1559
> URL: https://issues.apache.org/jira/browse/FLINK-1559
> Project: Flink
> Issue Type: Bug
> Components: Distributed Runtime
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 0.9
>
>
> Akka has the nasty property that it does not use IP addresses and hostnames
> interchangeably.
> Example: If the JobManager is started at
> {{akka:tcp//flink@localhost:1234/user/JOBMANAGER}} and a job client actor
> tries to send messages to {{akka:tcp//[email protected]:1234/user/JOBMANAGER}},
> the job manager actor system will receive the messages, but throw them away,
> because they are not destined for the actor system.
> I am not sure whether this is a bug or a feature in akka, but we need to deal
> with it. To be on the safe side, I suggest to build all akka URLs with ip
> addresses. We can still use host names in our logic (connection infos, local
> assignments, etc)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
