[
https://issues.apache.org/jira/browse/FLINK-32811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-32811:
-----------------------------------
Labels: pull-request-available (was: )
> Add port range support for taskmanager.data.bind-port
> -----------------------------------------------------
>
> Key: FLINK-32811
> URL: https://issues.apache.org/jira/browse/FLINK-32811
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration, Runtime / Coordination
> Reporter: Ferenc Csaky
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> Adding this feature could be helpful for installation in a restrictive
> network setup. The "port range" support is already available for some other
> port config options anyway.
> Right now, it is possible to specify a {{taskmanager.data.port}} and
> {{taskmanager.data.bind-port}} to be able to support NAT-like setups,
> although {{taskmanager.data.port}} is not bound to anything itself, so
> supporting a port range there is not an option according to my understanding.
> Although, supporting a port range only for {{taskmanager.data.bind-port}} can
> be still helpful for anyone who does not require a NAT capability, because if
> {{taskmanager.data.bind-port}} is set and {{taskmanager.data.port}} is set to
> *0*, then the bound port will be used everywhere.
> This change should keep the already possible setups working as is.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
