[
https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14738169#comment-14738169
]
Ted Yu commented on HBASE-6617:
-------------------------------
Patch v12 is on reviewboard.
Backport to branch-1 has been attached. Test failures were not caused by the
patch.
bq. for the LP stuff that's breaking
Can you clarify ? To my knowledge nothing is broken as of patch v12.
> 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: Yu Li
> Fix For: 2.0.0, 1.3.0
>
> Attachments: 6617-v11.patch, HBASE-6617.branch-1.patch,
> HBASE-6617.branch-1.v2.patch, HBASE-6617.patch, HBASE-6617_v10.patch,
> HBASE-6617_v11.patch, HBASE-6617_v12.patch, HBASE-6617_v2.patch,
> HBASE-6617_v3.patch, HBASE-6617_v4.patch, HBASE-6617_v7.patch,
> HBASE-6617_v9.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)
