You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bookkeeper.apache.org by "Ivan Kelly (JIRA)" <ji...@apache.org> on 2012/06/14 19:26:42 UTC
[jira] [Commented] (BOOKKEEPER-259) Create a topic manager using
versioned write for leader election
[ https://issues.apache.org/jira/browse/BOOKKEEPER-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13295175#comment-13295175 ]
Ivan Kelly commented on BOOKKEEPER-259:
---------------------------------------
I haven't reviewed this a great deal (pending questions on 250), but one issue is that HubInfo should be protobuf.
> Create a topic manager using versioned write for leader election
> ----------------------------------------------------------------
>
> Key: BOOKKEEPER-259
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-259
> Project: Bookkeeper
> Issue Type: Sub-task
> Components: hedwig-server
> Reporter: Sijie Guo
> Assignee: Sijie Guo
> Fix For: 4.2.0
>
> Attachments: BOOKKEEPER-259.diff, BOOKKEEPER-259.diff_v2
>
>
> currently, ZkTopicManager use zookeeper ephemeral node to store the owner information of a topic. so the znode will disappear when the owner hub server is down, the leader election is quite simple based on this model.
> but for most key-value storage, there is no similar concepts like ephemeral node, but just providing versioned writes. so it would be better to provide a topic manager using versioned writes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira