[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=17642246#comment-17642246 ] Yun Gao commented on FLINK-27341: - Merged on master via fc5e8bacef34119579defca6256476482da523f9 Merged on 1.15 via 84e8806af16f81a4295ca1f9b0c711c210884b1d Merged on 1.16 via 8a47420adfe9af7f1c303874c7a32dab3229ea66 > 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: Weihua Hu >Priority: Major > Labels: pull-request-available > > 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.10#820010)
[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=17634670#comment-17634670 ] Yun Gao commented on FLINK-27341: - Very thanks [~huwh] for the checking! I'll have a look. > 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: Weihua Hu >Priority: Major > Labels: pull-request-available > > 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.10#820010)
[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=17634637#comment-17634637 ] Weihua Hu commented on FLINK-27341: --- [~gaoyunhaii] I tested it in Kubernetes/Docker/Standalone. Rremoving the loopback works fine. Could you help review this PR. > 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: Weihua Hu >Priority: Major > Labels: pull-request-available > > 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.10#820010)
[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=17631543#comment-17631543 ] Weihua Hu commented on FLINK-27341: --- [~gaoyunhaii] yes, we can directly remove the LOOPBACK, i will do more tests in different deployment targets. > 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: Weihua Hu >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.10#820010)
[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=17631507#comment-17631507 ] Chesnay Schepler commented on FLINK-27341: -- It should be safe to just remove it imo. > 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: Weihua Hu >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.10#820010)
[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=17631342#comment-17631342 ] Yun Gao commented on FLINK-27341: - Hi [~chesnay] sorry for missing the comment, I also think we should drop the lookback address, but it may need some tests for different deployment targets. And very thanks [~huwh] for helping tracking this issue! I have assigned the issue to you. And for the method, do you think we might directly remove the LOOPBACK? I previously have some try with [https://github.com/gaoyunhaii/flink/pull/new/remove_loopback] and it should works in standalone session. > 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: Weihua Hu >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.10#820010)
[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=17629614#comment-17629614 ] Weihua Hu commented on FLINK-27341: --- Hi, [~chesnay] , [~gaoyunhaii] I think this was introduced by FLINK-24474. It uses the loopback address as the default address. In these configs, it only supports flink clusters running on a single host, and taskmanager must use the loopback interface to connect with the jobmanager, since the jobmanager only binds the loopback interface. But if we don't set the bind-address to localhost, taskmanager should not use the loopback interface to find its external address. otherwise, this will cause other TaskManagers to not connect with it. IMO, we can determine whether to use the loopback interface by whether the taskmanager.bind-host is loopback address. If this change is acceptable, you can assign this to me. > 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 >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.10#820010)
[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=17627128#comment-17627128 ] Chesnay Schepler commented on FLINK-27341: -- [~gaoyunhaii] What makes this so complicated? I thought we just have to drop the loopback address resolution strategy again. > 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.10#820010)
[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=17626508#comment-17626508 ] Yun Gao commented on FLINK-27341: - Hi [~nobleyd] sorry after I checked the code, it looks more complicated than I initially thought, thus I'm not very confident in changing this part of code right before the deadline without causing other issues and we'll move the fix after the release. I also still think the issue is critical and cause a lot of confusions, we are still working on this issue and will fix it soon. > 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.10#820010)
[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=17626171#comment-17626171 ] nobleyd commented on FLINK-27341: - Hi, this issue is not resolve in flink1.16, whilte I think it is important. [~gaoyunhaii] > 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.10#820010)
[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=17600640#comment-17600640 ] Yun Gao commented on FLINK-27341: - Hi [~nobleyd] If currently no other progress, I'll open a PR soon and try to make it included in 1.16. > 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.10#820010)
[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=17585171#comment-17585171 ] nobleyd commented on FLINK-27341: - Hi, I want to known which release will fix this issue, is there any plan? > 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.10#820010)
[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=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)
