[
https://issues.apache.org/jira/browse/HBASE-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14950357#comment-14950357
]
Ashish Singhi commented on HBASE-13153:
---------------------------------------
Thanks [~devaraj].
bq. One question - when the peer cluster does a bulkload, I am wondering if the
network is slow, would it hold up the peer RegionServer handlers for a longer
duration for bigger bulkloads, and thereby affect the throughput of the peer
cluster significantly.
A very valid point. I think this problem is not only related to replication but
also in a normal bulk load where source and destination hdfs clusters are
different. May be we can add a new QoS priority to handle bulk load ? and also
can we do that as part of another jira ?
> Bulk Loaded HFile 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-13153-v1.patch, HBASE-13153-v2.patch,
> HBASE-13153-v3.patch, HBASE-13153.patch, HBase Bulk Load
> Replication-v1-1.pdf, HBase Bulk Load Replication-v2.pdf, 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
(v6.3.4#6332)
