[
https://issues.apache.org/jira/browse/GIRAPH-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15332677#comment-15332677
]
Hudson commented on GIRAPH-1068:
--------------------------------
FAILURE: Integrated in Giraph-trunk-Commit #1621 (See
[https://builds.apache.org/job/Giraph-trunk-Commit/1621/])
GIRAPH-1068 Make Zookeeper accept 0 as a port number and let it choose (edunov:
[http://git-wip-us.apache.org/repos/asf?p=giraph.git&a=commit&h=916763e747b0f2d3bf2dcda76100dbc0d5714a9c])
* giraph-core/src/main/java/org/apache/giraph/zk/ZooKeeperManager.java
* giraph-core/src/main/java/org/apache/giraph/bsp/BspService.java
* giraph-core/src/main/java/org/apache/giraph/yarn/GiraphYarnClient.java
*
giraph-core/src/main/java/org/apache/giraph/zk/OutOfProcessZooKeeperRunner.java
* giraph-core/src/main/java/org/apache/giraph/zk/InProcessZooKeeperRunner.java
* giraph-core/src/main/java/org/apache/giraph/zk/ZookeeperConfig.java
* giraph-core/src/main/java/org/apache/giraph/bsp/BspInputFormat.java
* giraph-core/src/main/java/org/apache/giraph/utils/InternalVertexRunner.java
* giraph-core/src/main/java/org/apache/giraph/graph/GraphTaskManager.java
* giraph-core/src/main/java/org/apache/giraph/zk/ZooKeeperRunner.java
* giraph-core/src/main/java/org/apache/giraph/conf/GiraphConstants.java
* giraph-core/src/main/java/org/apache/giraph/conf/GiraphConfiguration.java
> Make Zookeeper accept 0 as a port number and let it choose any available free
> 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)
