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

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

Hi Jonathan, A BK backend for logging can potentially deal with the issues 
you're raising. The main issue is that it doesn't expose a file system 
interface, and HBase currently seems to rely upon one. If we have an interface 
that matches more naturally the BK api, then we will possibly be able to deal 
with the issues you're raising without much effort.

I was actually trying to implement a BookKeeperFS class that extends 
FileSystem, but it doesn't feel natural. I was wondering if we should try to 
work on the interface first instead of hacking it in by implementing an 
HLog.Reader and an HLog.Writer. 
                
> 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

        

Reply via email to