Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 27 Aug 2015 09:29:45 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12604086.1345484427000.180494.1440667785855@Atlassian.JIRA>
In-Reply-To: <JIRA.12604086.1345484427000@Atlassian.JIRA>
References: <JIRA.12604086.1345484427000@Atlassian.JIRA>
 <JIRA.12604086.1345484427576@arcas>
Subject: [jira] [Updated] (HBASE-6617) ReplicationSourceManager should be
 able to track multiple WAL paths
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Yu updated HBASE-6617:
--------------------------
    Status: Open  (was: Patch Available)

> 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
>
>
> 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)