Andrew Carman commented on ZOOKEEPER-30:

Harvey Mudd Clinic Team writes:

1) Is the assignment of zxid by Zab asynchronous? Otherwise, when calling 
propose we are going to have to wait for the proposal to be routed to the Zab 
leader, have it assign a zxid, return to the follower Zab, then return to the 
client, which seems like it could take a while if the connection is slow, or 
the leader gets bogged down.

2) What's the status of the proposal when propose returns? Just that the Zab 
leader has seen it or do we know it's been delivered?

3) The existing API doesn't appear to have any way to detect when another 
server comes online or goes offline. This seems like functionality that'd be 
useful in implementing ephemeral nodes. One possible solution might be to 
generalize the status() callback to indicate status changes to any node, not 
just the current node and leader.

4) Do the getState() and setState() callbacks really belong in the Zab API, or 
do they actually belong in the (so far theoretical) logging module? Whose 
state, exactly, is being transferred and stored?

> Hooks for atomic broadcast protocol
> -----------------------------------
>                 Key: ZOOKEEPER-30
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-30
>             Project: Zookeeper
>          Issue Type: New Feature
>            Reporter: Patrick Hunt
>            Assignee: Mahadev konar
> 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