[
https://issues.apache.org/jira/browse/FLINK-2722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902273#comment-14902273
]
ASF GitHub Bot commented on FLINK-2722:
---------------------------------------
Github user rmetzger commented on the pull request:
https://github.com/apache/flink/pull/1159#issuecomment-142221347
Thank you for the thorough review @tillrohrmann. I removed the
`resolveAddress()` method. It had a lot of duplicates with
`findConnectingAddress()` and was only used in one other location.
I'm now using the `findConnectingAddress()` there as well.
Regarding a test: There is a little test for `findConnectingAddress()`, but
we should add another test for the feature. My main problem is that I would
really like to include the fix into 0.10-milestone-1, which seems to be blocked
on this PR.
I'm currently manually testing my change on YARN to see if everything is
working as expected ...
> Use InetAddress.getLocalHost() first when detecting TaskManager IP address
> --------------------------------------------------------------------------
>
> Key: FLINK-2722
> URL: https://issues.apache.org/jira/browse/FLINK-2722
> Project: Flink
> Issue Type: Bug
> Components: Distributed Runtime, TaskManager
> Affects Versions: 0.9, 0.10
> Reporter: Robert Metzger
> Assignee: Robert Metzger
> Fix For: 0.9.2
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
