[
https://issues.apache.org/jira/browse/ZOOKEEPER-1080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13062861#comment-13062861
]
Hari A V commented on ZOOKEEPER-1080:
-------------------------------------
Thank you for reviewing the patch and your suggestions.
Yes, I can update the patch and change it to recipe.
Presently the patch (ZOOKEEPER-1080.patch) is failing due to the following
reason:-
I am using third party zkclient-0.1.0.jar (which is a wrapper over zookeeper
apis) for the implementation of leader-election service. The Hudson CI is not
picking this patch, instead it is picking only the zkclient.0.1.0.jar and its
failing.
Following are the couple of points, for choosing the zk-client.0.1.0.jar:
1: given more user friendly and meaningful apis like: subscribeChildChanges,
subscribeDataChanges, subscribeStateChanges, unsubscribe, unSubscribeAll,
deleteRecursive etc.
2: easy registeration and automatic re-registration of watches.
3: reconnection handling mechanism in case of timeout.
4: improved the efficiency of handling the events by introducing ZKEventThread
queue.
I feel, its better to include this jar into the zookeeper project. Other option
is, I needs to remove the dependency with the zkclient-0.1.0.jar and re-submit
the patch again.
Could you please suggest a good way to prepare patch which can be running in
Hudson CI.
Thanks & Regards,
Hari
> Provide a Leader Election framework based on Zookeeper receipe
> --------------------------------------------------------------
>
> Key: ZOOKEEPER-1080
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1080
> Project: ZooKeeper
> Issue Type: New Feature
> Components: contrib
> Affects Versions: 3.3.2
> Reporter: Hari A V
> Assignee: Hari A V
> Fix For: 3.4.0
>
> Attachments: LeaderElectionService.pdf, ZOOKEEPER-1080.patch,
> zkclient-0.1.0.jar, zookeeper-leader-0.0.1.tar.gz
>
>
> Currently Hadoop components such as NameNode and JobTracker are single point
> of failure.
> If Namenode or JobTracker goes down, there service will not be available
> until they are up and running again. If there was a Standby Namenode or
> JobTracker available and ready to serve when Active nodes go down, we could
> have reduced the service down time. Hadoop already provides a Standby
> Namenode implementation which is not fully a "hot" Standby.
> The common problem to be addressed in any such Active-Standby cluster is
> Leader Election and Failure detection. This can be done using Zookeeper as
> mentioned in the Zookeeper recipes.
> http://zookeeper.apache.org/doc/r3.3.3/recipes.html
> +Leader Election Service (LES)+
> Any Node who wants to participate in Leader Election can use this service.
> They should start the service with required configurations. The service will
> notify the nodes whether they should be started as Active or Standby mode.
> Also they intimate any changes in the mode at runtime. All other complexities
> can be handled internally by the LES.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
