[
https://issues.apache.org/jira/browse/GIRAPH-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Reisman updated GIRAPH-479:
-------------------------------
Description:
When the user does not specify a ZooKeeper quorum to run Giraph on, the
ZooKeeperManager creates one. This factors out the boilerplate that handles
this additional process and its lifecycle so that various pluggable versions of
this process instantiation can be implemented and fed to the ZKManager via a
factory depending on the nature of the underlying cluster.
By implementing the ZooKeeperProcessBuilder interface, one will now be able to
implement the creation/mangement of a new, job-local ZK instance using any
underlying resourcing mechanism one chooses (including, I hope, YARN.)
Passes mvn verify, etc.
Review board link:
https://reviews.apache.org/r/8948/
was:
When the user does not specify a ZooKeeper quorum to run Giraph on, the
ZooKeeperManager creates one. This factors out the boilerplate that handles
this additional process and its lifecycle so that various pluggable versions of
this process instantiation can be implemented and fed to the ZKManager via a
factory depending on the nature of the underlying cluster.
By implementing the ZooKeeperProcessBuilder interface, one will now be able to
implement the creation/mangement of a new, job-local ZK instance using any
underlying resourcing mechanism one chooses (including, I hope, YARN.)
Passes mvn verify, etc.
> Factor creation of job-local ZooKeeper instances out of ZKManager to enable
> YARN instantiation, etc.
> ----------------------------------------------------------------------------------------------------
>
> Key: GIRAPH-479
> URL: https://issues.apache.org/jira/browse/GIRAPH-479
> Project: Giraph
> Issue Type: Improvement
> Components: zookeeper
> Affects Versions: 0.2.0
> Reporter: Eli Reisman
> Assignee: Eli Reisman
> Priority: Minor
> Attachments: GIRAPH-479-1.patch, GIRAPH-479-2.patch
>
>
> When the user does not specify a ZooKeeper quorum to run Giraph on, the
> ZooKeeperManager creates one. This factors out the boilerplate that handles
> this additional process and its lifecycle so that various pluggable versions
> of this process instantiation can be implemented and fed to the ZKManager via
> a factory depending on the nature of the underlying cluster.
> By implementing the ZooKeeperProcessBuilder interface, one will now be able
> to implement the creation/mangement of a new, job-local ZK instance using any
> underlying resourcing mechanism one chooses (including, I hope, YARN.)
> Passes mvn verify, etc.
> Review board link:
> https://reviews.apache.org/r/8948/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
