[
https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708915#comment-14708915
]
Yu Li commented on HBASE-6617:
------------------------------
[~busbey] and [~tedyu],
It seems this work has no update for a while, and I'm not sure whether you're
still working on this. I have prepared a patch to solve this problem, could you
help review the patch and give some comments? Thanks.
The main thought of the fix here is to create one ReplicationSource for each
"wal group", and take the prefix of the log file name as the "wal group" name.
What's more, since we don't know how many "wal groups" there would be when
initializing ReplicationSourceManager, we can no longer initialize
ReplicationSource instances in the init method, but should do it in preLogRoll
instead. There're also some changes for multi-thread handling and UT fix,
please refer to the patch for details.
I have checked replication-relative UT with both defaultProvider and multiwal
using below command, and confirmed both could pass
{noformat}mvn -PlocalTests -Dtest=*Replication* clean test{noformat}
> ReplicationSourceManager should be able to track multiple WAL paths
> -------------------------------------------------------------------
>
> Key: HBASE-6617
> URL: https://issues.apache.org/jira/browse/HBASE-6617
> Project: HBase
> Issue Type: Improvement
> Components: Replication
> Reporter: Ted Yu
> Assignee: Sean Busbey
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-6617.patch
>
>
> Currently ReplicationSourceManager uses logRolled() to receive notification
> about new HLog and remembers it in latestPath.
> When region server has multiple WAL support, we need to keep track of
> multiple Path's in ReplicationSourceManager
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
