[jira] [Updated] (BOOKKEEPER-259) Create a topic manager using versioned write for leader election

["Sijie Guo (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/BOOKKEEPER-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sijie Guo updated BOOKKEEPER-259:
---------------------------------

    Attachment: BOOKKEEPER-259.diff

attach a new patch rebased on lastest trunk. the patch provide a topic manager using versioned write, so read/write owner info would be part to metadata manager as in BOOKKEEPER-250.
                
> 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
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-259.diff
>
>
> 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