Hi, this is definitely a bug you're describing. The problem is that with FLINK-2821 [1], we can no longer resolve the hostname on the JobManager. Thus, you should specify the external hostname of the machine on which you have started the JobManager (given that you've used the very same hostname for the jobmanager.rpc.address configuration value.
Now the actual problem is that ExecutionEnvironment.createRemoteEnvironment resolves the given hostname. This will lookup the hostname for the given ip. In contrast, the StreamExecutionEnvironment.createRemoteEnvironment won't do this. I think the latter should do the same to fix the problem. Can you open a JIRA issue for the problem? [1] https://issues.apache.org/jira/browse/FLINK-2821 Cheers, Till On Thu, Mar 30, 2017 at 2:41 PM, canbinzheng <2056268...@qq.com> wrote: > I run two examples in the same client. > > first one use / > ExecutionEnvironment.createRemoteEnvironment("10.75.203.170", 59551)/ > second one use > /StreamExecutionEnvironment.createRemoteEnvironment("10.75.203.170", > 59551)/ > > the first example run successfully, but the second example failed(connect > to > akka timeout), for the second one, if I change host parameter from ip to > hostname, it works. > > I check the source code, and I found the ip would be translated into > hostname automatically in the first example, but the second one don't. > > I am so confused if the ActorRef must use hostname as part of address, not > ip? is it a bug? > > > > > -- > View this message in context: http://apache-flink-mailing- > list-archive.1008284.n3.nabble.com/Bug-Question-about- > StreamExecutionEnvironment-createRemoteEnvironment-tp16854.html > Sent from the Apache Flink Mailing List archive. mailing list archive at > Nabble.com. >
