[
https://issues.apache.org/jira/browse/HBASE-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745466#comment-14745466
]
Bhupendra Kumar Jain commented on HBASE-13153:
----------------------------------------------
Thanks all for reviewing the design. One small update.
As per earlier design, we are keeping references of hfiles into ZK to avoid
hfile clean up before replication is finished. There is small change require in
design to handle multiple peer cluster replication scenario. These hfile
references needs to be maintained in zk for each peer based on replication
scope enabled for that peer.
Once the replication of hfile for any of the peer is successfully done,
corresponding zk reference entry will be cleared. We will also update the
design doc with this change.
> 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-v1-1.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)
