[
https://issues.apache.org/jira/browse/HBASE-15537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15219209#comment-15219209
]
Duo Zhang commented on HBASE-15537:
-----------------------------------
Talked with [~carp84] offline, he had some concerns on the structure that we
nest WALProviders inside another WALProvider.
Actually we have two separated logics here. One is how the WALs are grouped(One
WAL for all, or group WALs by region), and the other is how to create a
specific WAL(FSHLog, AsyncFSWAL, etc.).
In the current architecture, all the logics are placed in WALProvider so the
proper way to address this issue is to nest WALProvider inside another
WALProvider. And I think it is better to separate the two logics into different
classes, but it requires a big refactoring.
What do you think? [~stack]
Thanks.
> 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)
