You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Zhihong Ted Yu (JIRA)" <ji...@apache.org> on 2012/06/22 10:50:48 UTC

[jira] [Comment Edited] (HBASE-2315) BookKeeper for write-ahead logging

    [ https://issues.apache.org/jira/browse/HBASE-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13399220#comment-13399220 ] 

Zhihong Ted Yu edited comment on HBASE-2315 at 6/22/12 8:50 AM:
----------------------------------------------------------------

Here is the JIRA that tracks parallel hdfs writes:
HBASE-6116 Allow parallel HDFS writes for HLogs

HBASE-5699 would allow multiple WALs per region server. Grouping of edits can be per-table or, one WAL per region.
WAL interface abstraction appears in the discussion there.

Feel free to propose WAL interface for this JIRA.
                
      was (Author: zhihyu@ebaysf.com):
    Here is the JIRA that tracks parallel hdfs writes:
HBASE-6116 Allow parallel HDFS writes for HLogs

HBASE-5699 would allow multiple WALs per region server. WAL interface abstraction appears in the discussion there.

Feel free to propose WAL interface for this JIRA.
                  
> BookKeeper for write-ahead logging
> ----------------------------------
>
>                 Key: HBASE-2315
>                 URL: https://issues.apache.org/jira/browse/HBASE-2315
>             Project: HBase
>          Issue Type: New Feature
>          Components: regionserver
>            Reporter: Flavio Junqueira
>         Attachments: HBASE-2315.patch, bookkeeperOverview.pdf, zookeeper-dev-bookkeeper.jar
>
>
> BookKeeper, a contrib of the ZooKeeper project, is a fault tolerant and high throughput write-ahead logging service. This issue provides an implementation of write-ahead logging for hbase using BookKeeper. Apart from expected throughput improvements, BookKeeper also has stronger durability guarantees compared to the implementation currently used by hbase.

--
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