You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org> on 2010/05/17 10:47:46 UTC

[jira] Commented: (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=12868133#action_12868133 ] 

Flavio Paiva Junqueira commented on HBASE-2315:
-----------------------------------------------

Just a couple of quick points about the developments of this jira:

# We have introduced deletion and garbage collection of ledgers to BookKeeper (ZOOKEEPER-464);
# Our next goal as far as features for bookkeeper goes is ZOOKEEPER-712 (see my previous post);
# I have started benchmarking hbase+bookkeeper with the Yahoo! benchmark, but I stumbled upon a problem. When I wrote this preliminary patch, I didn't have a nice way of creating a unique znode name and keeping it for fetching the last log of a region server, given the current interface of WAL. My understanding of the code is that the hdfs file where the is stored is passed to the reader/writer. I'm considering the current hdfs path as the znode path (or at least a part of it), but I would accept suggestions if anyone is willing to give me one.

> BookKeeper for write-ahead logging
> ----------------------------------
>
>                 Key: HBASE-2315
>                 URL: https://issues.apache.org/jira/browse/HBASE-2315
>             Project: Hadoop HBase
>          Issue Type: New Feature
>          Components: regionserver
>            Reporter: Flavio Paiva Junqueira
>         Attachments: bookkeeperOverview.pdf, HBASE-2315.patch, 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.
-
You can reply to this email to add a comment to the issue online.