[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219335#comment-15219335
]
Sean Busbey commented on HBASE-15537:
-------------------------------------
IMHO, nesting WALProviders is the correct way to do this. up until HBASE-14448,
multiwal did that nesting; i.e. GroupingProvider just handled mapping Regions
to WALProvider instances and the actual WAL was configurable.
Probably the changes in HBASE-14448 should have cached WAL instances instead of
FSHLog instances. If you switch to that and put back in the delegate WAL
creation from before HBASE-14448 then adding in a provider that creates
AsyncFSWAL instead of the default FSHLog should be straight forward.
> 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
>
>
> The multi WAL should not be bound with {{FSHLog}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
