[
https://issues.apache.org/jira/browse/FLINK-6224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-6224:
----------------------------------
Labels: auto-deprioritized-major auto-unassigned patch (was:
auto-unassigned patch stale-major)
Priority: Minor (was: Major)
This issue was labeled "stale-major" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Major, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> RemoteStreamEnvironment not resolve ip of JobManager to hostname
> ----------------------------------------------------------------
>
> Key: FLINK-6224
> URL: https://issues.apache.org/jira/browse/FLINK-6224
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream, Command Line Client
> Affects Versions: 1.2.0
> Reporter: CanBin Zheng
> Priority: Minor
> Labels: auto-deprioritized-major, auto-unassigned, patch
>
> 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 one runs successfully, but the second fails(connect to JobManager
> timeout), for the second one, if I change host parameter from ip to hostname,
> it works.
> I checked the source code and found,
> ExecutionEnvironment.createRemoteEnvironment
> resolves the given hostname, this will lookup the hostname for the given
> ip. In contrast, the StreamExecutionEnvironment.createRemoteEnvironment
> won't do this.
> As Till Rohrmann mentioned, the problem is that with
> FLINK-2821 [1], we can no longer resolve the hostname on the JobManager, so,
> we'd better resolve hostname for given ip in RemoteStreamEnvironment too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
