You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2022/04/21 13:53:00 UTC

[jira] [Commented] (FLINK-27341) TaskManager running together with JobManager are bind to 127.0.0.1

    [ https://issues.apache.org/jira/browse/FLINK-27341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17525730#comment-17525730 ] 

Chesnay Schepler commented on FLINK-27341:
------------------------------------------

We're currently checking if the loopback address resolution strategy is still necessary; if not we may be able to remove it or hide it behind a feature flag. The recent fixes around yarn related to FLINK-24474 may have removed the "need" for it. (Quotation marks because I think we were only fighting symptoms).

> TaskManager running together with JobManager are bind to 127.0.0.1
> ------------------------------------------------------------------
>
>                 Key: FLINK-27341
>                 URL: https://issues.apache.org/jira/browse/FLINK-27341
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.15.0, 1.16.0
>            Reporter: Yun Gao
>            Assignee: Chesnay Schepler
>            Priority: Major
>
> If some TaskManagers running with JobManager on the same machine while some other TaskManager not, the TaskManagers running together with JobManager would bind to localhost or 127.0.01, which makes the Netty connections across the TaskManagers fail.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)