hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Busbey (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6617) ReplicationSourceManager should be able to track multiple WAL paths
Date Fri, 19 Dec 2014 16:52:14 GMT

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

Sean Busbey updated HBASE-6617:
    Fix Version/s: 1.1.0

Copied from my follow up on HBASE-5699's rb

there's an optimization of sorts still outstanding with HBASE-6617. Essentially, the replication
code keeps around the last wal it saw so that when a new replication target comes online there's
something to give it right away. HBASE-6617 would make it keep one-per-provider so that in
the case of multiwal you don't just have 1/n of the entries you would have had with a single

As is, if someone enables multiwal prior to HBASE-6617 getting finished they'll have fewer
recent entries replayed as a new source comes online, but things will still function as expected
from that point on.

> 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.1.0
> 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

View raw message