[
https://issues.apache.org/jira/browse/FLINK-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16908201#comment-16908201
]
Robert Fiser commented on FLINK-13717:
--------------------------------------
Binding to 0.0.0.0 starts listening on all visible interfaces so there
shouldn't be a problem.
If your point is that taskmanager should always starts listening at 0.0.0.0 and
the property `taskmanager.host` will be used only to registration it probably
fits our requirements. But I'm not sure that listening on all interfaces is a
good practice - not admin or network expert.
> 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
(v7.6.14#76016)
