Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flink.apache.org
Date: Fri, 14 Aug 2015 10:04:46 +0000 (UTC)
From: "Till Rohrmann (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12856119.1439546667000.66050.1439546686391@Atlassian.JIRA>
In-Reply-To: <JIRA.12856119.1439546667000@Atlassian.JIRA>
References: <JIRA.12856119.1439546667000@Atlassian.JIRA>
 <JIRA.12856119.1439546667539@arcas>
Subject: [jira] [Created] (FLINK-2518) Avoid predetermination of ports for
 network services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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)