flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fabian Hueske (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (FLINK-2518) Avoid predetermination of ports for network services
Date Mon, 16 Nov 2015 13:44:14 GMT

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

Fabian Hueske updated FLINK-2518:
---------------------------------
    Fix Version/s:     (was: 0.10.0)
                   1.0.0

> 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: 1.0.0
>
>
> 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)

Mime
View raw message