[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219310#comment-15219310
]
stack commented on HBASE-15537:
-------------------------------
[~busbey] Your opinion appreciated here.
A provider inside a provider sounds right -- it is the proper separation -- but
not sure our APIs as they are are amenable to cascading like this. Given it was
Sean who did the first cut at multi, my guess is that he considered this and
probably has some better input than I here.
Does this current patch work? If it does, would be worth trying a compare.
Async might help make better define the case for multiwal.
> 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)
