You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2016/04/04 15:33:25 UTC

[jira] [Updated] (FLINK-3451) NettyServer port is determined via NetUtils.getAvailablePort()

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

Ufuk Celebi updated FLINK-3451:
-------------------------------
    Assignee:     (was: Ufuk Celebi)

> NettyServer port is determined via NetUtils.getAvailablePort()
> --------------------------------------------------------------
>
>                 Key: FLINK-3451
>                 URL: https://issues.apache.org/jira/browse/FLINK-3451
>             Project: Flink
>          Issue Type: Bug
>          Components: Distributed Runtime
>            Reporter: Ufuk Celebi
>
> During start up, the {{NettyServer}} port is configured via {{NetUtils.getAvailablePort()}}. In most cases, this works as expected, but it is possible that another service grabs the port while it is available (between the check and {{NettyServer}} initialization).
> It is more robust to let {{NettyServer}} pick the port itself no port is specified.
> In general the {{getAvailablePort-then-setConfig}} pattern is not recommended.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)