[
https://issues.apache.org/jira/browse/FLINK-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224123#comment-15224123
]
Ufuk Celebi commented on FLINK-3451:
------------------------------------
This is not easy to implement, because of the way that the task managers setup
and connect to the job manager.
> 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)
