[jira] [Updated] (HBASE-6617) ReplicationSourceManager should be able to track multiple WAL paths

["Yu Li (JIRA)" <ji...@apache.org>]

     [ 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_v7.patch

Sync-up with [rb|https://reviews.apache.org/r/37717/]

After an offline discussion with Chunhui, I agreed to take the new design. In the new design, we will launch multiple threads(in name of ReplicationSourceWorkerThread) to track multiple wal groups inside ReplicationSource, thus keeping the changes inside ReplicationSource to minimize the affect to the outer part.

The uploaded v7 patch is based on the new design, and got all Replication UT cases passed with both default provider and multiwal provider.

[~busbey], [~tedyu] and [~zjushch], Please help review the new patch, and let me know your thoughts. Thanks.

> 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: HBASE-6617.patch, HBASE-6617_v2.patch, HBASE-6617_v3.patch, HBASE-6617_v4.patch, HBASE-6617_v7.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)