GitHub user rmetzger opened a pull request:
https://github.com/apache/flink/pull/1159
[FLINK-2722] Use InetAddress.getLocalHost() as first approach when
detecting the TMs own ip/hostname
A user reported a connection issue with Netty being unable to connect to a
TaskManager to subscribe to an intermediate result.
The problem occurred when the TaskManager and JobManager were running on
the same host (something that can easily happen on YARN).
In that case, the TaskManager was reporting a host-local ip address to the
JobManager when connecting.
To avoid the issue in the future, the TaskManager first tries to use the
hostname returned by InetAddress.getLocalHost(). In a properly set-up
environment, this will return a connection which is accessible by all machines
in a cluster.
I tested this implementation on a cluster in GCE using YARN (note that I
was not able to reproduce the issue originally reported, but the user reported
that the issue has been fixed)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rmetzger/flink network_detection_0.10
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1159.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1159
----
commit f9913e731f44c0c84e83670dfe35d2c4ead09a4a
Author: Robert Metzger <[email protected]>
Date: 2015-09-04T12:51:40Z
[FLINK-2722] Use InetAddress.getLocalHost() as first approach when
detecting the TMs own ip/hostname
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
