You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Till Rohrmann (JIRA)" <ji...@apache.org> on 2015/08/14 12:04:46 UTC
[jira] [Created] (FLINK-2518) Avoid predetermination of ports for
network services
Till Rohrmann created FLINK-2518:
------------------------------------
Summary: Avoid predetermination of ports for network services
Key: FLINK-2518
URL: https://issues.apache.org/jira/browse/FLINK-2518
Project: Flink
Issue Type: Improvement
Reporter: Till Rohrmann
Fix For: 0.10
Some of Flink's network services use the {{NetUtils.getAvailablePort()}} to predetermine an available port for a service which is later started. This can lead to a race condition where two services have predetermined the same available port and later fail to instantiate because for one of them the port is already in use.
This is, for example, the case for the {{NettyConnectionManager}} which is started after the {{TaskManager}} has registered at the {{JobManager}}. It would be better if we first start the network services with a random port, e.g. the {{NettyConnectionManager}}, and then send the bound port to the client. This will avoid problems like that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)