hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yu Li (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6617) ReplicationSourceManager should be able to track multiple WAL paths
Date Mon, 24 Aug 2015 08:11:45 GMT

    [ https://issues.apache.org/jira/browse/HBASE-6617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708924#comment-14708924

Yu Li commented on HBASE-6617:

Sorry that somehow I neglected this comment when adding the comment to attach the patch. The
problem here is that in case there're multiple wal groups, log roll of one group might clean
up the not-replicated-yet log of the other group, especially considering the log set is sorted
by the log name.

Take BoundedRegionGroupingProvider for example, assuming using the default group number 2,
then we will have two wal groups, say "<providerId>-0" and "<providerId>-1", if
the log in "<providerId>-1" group got more writes and rolled first, then all wals in
"<providerId>-0" will got removed unexpectedly

> 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.3.0
>         Attachments: HBASE-6617.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

View raw message