[jira] [Moved] (BOOKKEEPER-692) TeaKeeper: Hot standby support using bookkeeper

["Patrick Hunt (JIRA)" <ji...@apache.org>]

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

Patrick Hunt moved ZOOKEEPER-1016 to BOOKKEEPER-692:
----------------------------------------------------

        Key: BOOKKEEPER-692  (was: ZOOKEEPER-1016)
    Project: Bookkeeper  (was: ZooKeeper)

> TeaKeeper: Hot standby support using bookkeeper
> -----------------------------------------------
>
>                 Key: BOOKKEEPER-692
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-692
>             Project: Bookkeeper
>          Issue Type: Improvement
>            Reporter: Ivan Kelly
>            Assignee: Ivan Kelly
>            Priority: Minor
>         Attachments: tledger.pdf, tledger.pdf
>
>
> Currently Bookkeeper provides functionality for cold backups. If the entity logging to bookkeeper fails, its replacement must recover the ledgers which had been used for backup before becoming available. This is acceptable in some cases, such as HBase Wals where a small delay in recovery only results in a small percentage of data being unavailable. 
> However, systems such as the HDFS namenode, this delay can be unacceptable, such as cases where data is being served to customers. Secondary namenodes should be ready to go the instant the primary goes down.
> TeaKeeper proposes a wrapper library around Bookkeeper providing T-Junction like functionality for logging. It also provides for primary/secondary election and automated hot failover. 
> HDFS namenode is primary target of this work.
> The attached design doc contains more details.



--
This message was sent by Atlassian JIRA
(v6.1#6144)