[
https://issues.apache.org/jira/browse/HBASE-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14725362#comment-14725362
]
ramkrishna.s.vasudevan commented on HBASE-13153:
------------------------------------------------
Thanks Ashish. Had an offline discussion. I was thinking on the HFiles that are
being replicated but are moved to archive due to compaction. Here again we
need to retry the operation like in case of WAL as per discussion with Ashish.
Few things to consider, ensure that if there is block encoding then the
encoding scheme is same in both the tables. These type of conditions may come
in the initial pre checks that we may need to add.
> 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
(v6.3.4#6332)
