Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 2 Sep 2015 14:55:46 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12779355.1425467541000.235918.1441205746828@Atlassian.JIRA>
In-Reply-To: <JIRA.12779355.1425467541000@Atlassian.JIRA>
References: <JIRA.12779355.1425467541000@Atlassian.JIRA>
 <JIRA.12779355.1425467541610@arcas>
Subject: [jira] [Commented] (HBASE-13153) enable bulkload to support
 replication
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Ted Yu commented on HBASE-13153:
--------------------------------

bq. unique cluster id of all source hbase clusters will be persisted in ZK of Peer cluster under hfile replication node

When would hfile replication node in ZK be cleared / removed ?

> 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)