[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-15537:
--------------------------
Attachment: HBASE-15537_v2.patch
After a second thought, the nesting WALProviders way before HBASE-14448 seems
to follow the decorator pattern, and we could let RegionGroupingProvider focus
on handling the grouping stuff while delegating WAL creation/roll/close to
default/async provider, so I think I should change my mind to support it.
[~busbey] I wish you had stopped me during HBASE-14448 sir. :-)
OTOH, I think the design of nesting providers is not that straight forward to
understand, so I suggest to add some javadoc to explain.
I made some changes to get back the hbase.wal.regiongrouping.delegate.provider
property, and simply set it to *asyncfs* will enable AsyncFSWAL. I also did
some sanity test through TestReplicationSyncUpToolWithMultipleWAL and confirmed
it works well with multiple async WAL.
Attached is the updated patch, just for your information [~Apache9].
> Add multi WAL support for AsyncFSWAL
> ------------------------------------
>
> Key: HBASE-15537
> URL: https://issues.apache.org/jira/browse/HBASE-15537
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-15537.patch, HBASE-15537_v2.patch
>
>
> The multi WAL should not be bound with {{FSHLog}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
