You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (Jira)" <ji...@apache.org> on 2020/01/20 11:18:00 UTC
[jira] [Updated] (FLINK-13717) allow to set taskmanager.host and
taskmanager.bind-host separately
[ https://issues.apache.org/jira/browse/FLINK-13717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen updated FLINK-13717:
---------------------------------
Labels: usability (was: )
> 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
> Labels: usability
>
> 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.4#803005)