[ https://issues.apache.org/jira/browse/FLINK-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16911066#comment-16911066 ]
Robert Fiser edited comment on FLINK-13717 at 8/20/19 7:22 AM: --------------------------------------------------------------- I don't think that just default listening on _0.0.0.0_ will fit. By default I mean without specifying _taskmanager.host_. We need to register taskmanager with external host/address and the process doesn't know it without specifying via config so it would be registered with zeroes or container host/address which is not visible in cluster. The only minimum scenario that fits our requirements is to always listening on zeroes and register taskmanager with _taskmanager.host_ and system default. But as I said before I don't think it is a good practice to listening always on zeores(all visible interfaces). was (Author: fiserro): I don't think that just default listening on 0.0.0.0 will fit. By default I mean without specifying /taskmanager.host/. We need to register taskmanager with external host/address and the process doesn't know it without specifying via config so it would be registered with zeroes or container host/address which is not visible in cluster. The only minimum scenario that fits our requirements is to always listening on zeroes and register taskmanager with /taskmanager.host/ and system default. But as I said before I don't think it is a good practice to listening always on zeores(all visible interfaces). > allow to set taskmanager.host and taskmanager.bind-host separately > ------------------------------------------------------------------ > > Key: FLINK-13717 > URL: https://issues.apache.org/jira/browse/FLINK-13717 > Project: Flink > Issue Type: New Feature > Components: Runtime / Configuration, Runtime / Network > Affects Versions: 1.8.1, 1.9.0 > Reporter: Robert Fiser > Priority: Major > > We trying to use flink in docker container with bridge network. > Without specifying taskmanager.host taskmanager binds the host/address which > is not visible in cluster. It's same behaviour when taskmanager.host is set > to 0.0.0.0. > When it is se to external address or host name then taskmanager cannot bind > the address because of bridge network. > So we need to set taskmanager.host which will be reported to jobmanager and > taskmanager.bind-host which can taskmanager bind inside the container > It similar to https://issues.apache.org/jira/browse/FLINK-2821 but the > problem is with taskmanagers. -- This message was sent by Atlassian Jira (v8.3.2#803003)