Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@giraph.apache.org
Date: Thu, 2 Jun 2016 19:08:59 +0000 (UTC)
From: "Sergey Edunov (JIRA)" <jira@apache.org>
To: giraph-dev@incubator.apache.org
Message-ID: <JIRA.12975269.1464894511000.18426.1464894539261@Atlassian.JIRA>
In-Reply-To: <JIRA.12975269.1464894511000@Atlassian.JIRA>
References: <JIRA.12975269.1464894511000@Atlassian.JIRA> <JIRA.12975269.1464894511794@arcas>
Subject: [jira] [Created] (GIRAPH-1068) Make Zookeeper accept 0 as a port
 number and let it choose free available port
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Jun 2016 19:09:01 -0000

Sergey Edunov created GIRAPH-1068:
-------------------------------------

             Summary: Make Zookeeper accept 0 as a port number and let it choose free available port
                 Key: GIRAPH-1068
                 URL: https://issues.apache.org/jira/browse/GIRAPH-1068
             Project: Giraph
          Issue Type: Task
            Reporter: Sergey Edunov
            Assignee: Sergey Edunov


We have a few use cases where having zookeeper bound to specific port is very inconvenient. 
1) Unit tests that run in parallel. 
2) Shared clusters where multiple giraph instances can run on the same machines. 

In theory we don't need to know what port zookeeper will run on. In most cases we're fine with any port available. 
Picking any available port is currently supported by the server socket, but is not supported in the code that parses zookeper configs (this code lives in zookeper). 
We don't have to parse configs though, as we have a way to run zookeper in process. And in that case we can have a full control on how zookeeper is initialized. 

For this task I want to allow 0 as a port number for zookeeper. Which will allow us to run zookeeper on any available port. And I will also remove "out of process" zookeeper, as it clearly provides no benefits to us.  

Note: it will still be possible to run external zookeper, if you have it running somewhere as a service. 


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