[
https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yu Li updated HBASE-6617:
-------------------------
Attachment: HBASE-6617_v12.patch
Fix UT failures in the new patch.
The configuration used for multiwal in the newly-added UT cases in patch v11
was based on HBASE-14306, which will cause ClassNotFound issue in current code
base.
Also checked the UT failure of TestImportExport#testImport94Table and
TestProcessBasedCluster#testHomePath, both could pass on my local run. Let's
see what HadoopQA will say with the new patch.
> 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.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)
