[ 
https://issues.apache.org/jira/browse/ZOOKEEPER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12695645#action_12695645
 ] 

Andrew Farmer commented on ZOOKEEPER-30:
----------------------------------------

Other Andrew here. (I'm also on the HMC clinic team.)

Basically, the issue is that a lot of the changes we made have been kind of 
"patch-unfriendly" - we've moved and renamed a lot of files, and that can't 
really be reflected well by a patch file. (We tried generating a straight patch 
between our repository and yours, and it ended up being something like 5 MB.)

With that all in mind, though, I'm attaching a REALLY ROUGH patch that simply 
adds our current version of Zab, as well as its respective tests, to the 
current SVN trunk revision of Zookeeper. Hopefully this should resolve the 
legal issues.

What it doesn't do is:

1) It doesn't make Zookeeper use Zab for anything. As a result, there's a lot 
of duplicated code now - Zookeeper *will* need to be modified significantly to 
run against the Zab API.

2) It also doesn't port in some of the changes you folks have made to code 
that's within Zab's ambit. (What's included is basically everything that 
doesn't involve either clients or the data tree: leader election, proposal 
handling, and logging/persistence.)

3) Finally, it's not quite complete. We're still working on implementing syncs, 
as well as doing some further tests.

Hopefully this is enough to start taking a look at, though...

> Hooks for atomic broadcast protocol
> -----------------------------------
>
>                 Key: ZOOKEEPER-30
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-30
>             Project: Zookeeper
>          Issue Type: New Feature
>          Components: quorum
>            Reporter: Patrick Hunt
>            Assignee: Mahadev konar
>         Attachments: zab.diff
>
>
> Moved from SourceForge to Apache.
> http://sourceforge.net/tracker/index.php?func=detail&aid=1938788&group_id=209147&atid=1008547

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to