[
https://issues.apache.org/jira/browse/FLINK-8623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16392849#comment-16392849
]
ASF GitHub Bot commented on FLINK-8623:
---------------------------------------
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/5449
This breaks the expected behavior, unfortunately.
The logic is as follows:
- try to connect to JM / RM / ZK and use an interface that you can
connect from, if possible
- if that does not work, fall back to your default interface
(`getLocalHost()`) - the heuristic
If we change step 2 to use `getByName("localhost")` it gives us the
loopback interface which no one external can connect to. That would basically
mean that TM is isolated for any data communication.
The change to `ConnectionUtils` cannot be made like this. Instead, I would
suggest to look at why the instability happens and fix the test instead (retry
or a better test approach).
> ConnectionUtilsTest.testReturnLocalHostAddressUsingHeuristics unstable on
> Travis
> --------------------------------------------------------------------------------
>
> Key: FLINK-8623
> URL: https://issues.apache.org/jira/browse/FLINK-8623
> Project: Flink
> Issue Type: Bug
> Components: Tests
> Affects Versions: 1.5.0
> Reporter: Till Rohrmann
> Priority: Blocker
> Labels: test-stability
> Fix For: 1.5.0, 1.4.3
>
>
> {{ConnectionUtilsTest.testReturnLocalHostAddressUsingHeuristics}} fails on
> Travis: https://travis-ci.org/apache/flink/jobs/339344442
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
