[
https://issues.apache.org/jira/browse/HBASE-13153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727577#comment-14727577
]
Ashish Singhi commented on HBASE-13153:
---------------------------------------
bq. When would hfile replication node in ZK be cleared / removed ?
HFile node will be deleted by the source cluster based on the response from the
peer cluster.
At the peer cluster a hfile replication will be treated as successful only
after it has been successfully loaded and after a successful notification about
this hfiles to its peer clusters if its finds any and which is not among any of
the source clusters.
A notification will be treated successful only after it is able to add this
hfile entry to the ZK.
> 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)
