[
https://issues.apache.org/jira/browse/HBASE-17437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15812424#comment-15812424
]
Yishan Yang commented on HBASE-17437:
-------------------------------------
Yeah, we used to use WAL, but from doc, default.xml, etc. On code side, it
always use WAL, but from user side, hlog has much more occurrence. (Like 100 to
16). We already deployed it into our production and a lot of customer are using
it right now. We passed integration tests , performance tests, unit tests. Up
till now, there is no complain about this deployment yet.
Thanks for your feed back!
> Support specifying a WAL directory outside of the root directory
> ----------------------------------------------------------------
>
> Key: HBASE-17437
> URL: https://issues.apache.org/jira/browse/HBASE-17437
> Project: HBase
> Issue Type: Improvement
> Components: Filesystem Integration, wal
> Affects Versions: 1.2.4
> Reporter: Yishan Yang
> Assignee: Yishan Yang
> Labels: patch
> Fix For: 2.0.0, 1.4.0
>
> Attachments: hbase-17437-branch-1.2.patch, hbase-17437-master.patch
>
>
> Currently, the WAL and the StoreFiles need to be on the same FileSystem. Some
> FileSystems (such as Amazon S3) don’t support append or consistent writes.
> These two properties are imperative for the WAL in order to avoid loss of
> writes. However, StoreFiles don’t necessarily need the same consistency
> guarantees (since writes are cached locally and if writes fail, they can
> always be replayed from the WAL).
>
> This JIRA aims to allow users to configure a log directory (for WALs) that is
> outside of the root directory or even in a different FileSystem. The default
> value will still put the log directory under the root directory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
