hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashish Singhi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-13153) enable bulkload to support replication
Date Tue, 01 Sep 2015 12:57:47 GMT

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

Ashish Singhi commented on HBASE-13153:

Thanks [~ram_krish] for the review and comments.
bq. Can you explain more on this? This will get registered as how the WalActionsListener get
registered right?
More, is explained by yourself in the next question :-) and answer for that is yes.

bq. One thing to note is that if you are not allowing the hfiles to be archived that is due
to compaction will it not be removed from the block cache also? Till the replication is done
we will have it in the block cache also? See to this point. In a real case this file may not
be actually referred but it may be in the block cache for some time till it gets evicted.
I need to see this code if really this is happening. If so no problem. May be a small prototype
on this area of the feature will help you when going in for the full impl.
No, we will not disallow hfiles from being archived. Existing source logic related to compaction
and block cache will remain as it is. We will only not allow hfiles to get deleted until and
unless it is successfully replicated, which will similar to the existing WAL implementation.

> enable bulkload to support replication
> --------------------------------------
>                 Key: HBASE-13153
>                 URL: https://issues.apache.org/jira/browse/HBASE-13153
>             Project: HBase
>          Issue Type: New Feature
>          Components: Replication
>            Reporter: sunhaitao
>            Assignee: Ashish Singhi
>             Fix For: 2.0.0
>         Attachments: HBase Bulk Load Replication.pdf
> Currently we plan to use HBase Replication feature to deal with disaster tolerance scenario.But
we encounter an issue that we will use bulkload very frequently,because bulkload bypass write
path, and will not generate WAL, so the data will not be replicated to backup cluster. It's
inappropriate to bukload twice both on active cluster and backup cluster. So i advise do some
modification to bulkload feature to enable bukload to both active cluster and backup cluster

This message was sent by Atlassian JIRA

View raw message