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 17:20:46 GMT

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

Yu Li commented on HBASE-6617:

Yes, actually in current master branch if we set provider to mutiwal there will be more UT
failures besides this one, that's why I only mentioned to make sure all *Replication* UT cases
could pass in previous comment. I'd like to open another JIRA to fix the non-replication UT
failures while leaving this JIRA focusing on replication, do you think this ok [~tedyu]?

Actually we have done more work to complete multiple wal solution in product cluster and the
data in our product env shows good performance improvement, and I plan to contribute the work
back as much as possible, but choose to start from fixing the existing issues, since the other
work (including other UT failure fix) involve some refactor on the wal provider framework
(I personally think the current provider over provider design is not necessary or clear enough)
and needs more discussion.

> 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