[
https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746897#comment-17746897
]
Junrui Li edited comment on FLINK-32669 at 7/25/23 10:19 AM:
-------------------------------------------------------------
IIUC, the default value of the configuration item taskmanager.data.port is 0,
which means that an idle port will be randomly selected, so generally speaking,
no port conflicts will occur. Could you please explain in detail the scenario
where port conflicts will occur if this configuration item is not set?
was (Author: JIRAUSER293716):
IIUC, the default value of the configuration item taskmanager.data.port is 0,
which means that an idle port is randomly selected, so generally speaking, no
port conflicts will occur. Could you please explain in detail the scenario
where port conflicts will occur if this configuration item is not set?
> Support range-port for taskmanager data port
> --------------------------------------------
>
> Key: FLINK-32669
> URL: https://issues.apache.org/jira/browse/FLINK-32669
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Network
> Reporter: chenyuzhi
> Priority: Major
>
> We can setup range-port for taskmanager rpc port to avoid occupying an
> unexpected port(such as the port of datanode service).
>
> However, we can't setup range-port for taskmanager data port(config-key:
> taskmanager.data.port). In production env, it's unreasonable to setup a
> specify port, thus we usually not setup this configuration key.
>
> The problem is without setup taskmanager data port, it's possible to conflict
> with port of other services. Thus is it necessary to support range-port for
> taskmanager data port ?
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
