[ 
https://issues.apache.org/jira/browse/FLINK-32669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

chenyuzhi updated FLINK-32669:
------------------------------
    Description: 
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 

 

必要的

  was:
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 can conflict with port 
of other services .
It means still can be port conflict 
不合理


> Support port-range 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 
>  
> 必要的



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to