[
https://issues.apache.org/jira/browse/HBASE-2315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12898424#action_12898424
]
Benjamin Reed commented on HBASE-2315:
--------------------------------------
we looked into the problem of figuring out the path to use for the WAL and
found the following: it appears that the assumption that the WAL is stored in
HDFS is embedded in HBase. when looking up a WAL, for example, the FileSystem
object is used to check existence. Deletion of logs also happens outside of the
WAL interfaces. to be truly pluggable a WAL interface should be used to
enumerate and delete logs. have you guys thought about doing this?
> 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: 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.
