Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 2 Sep 2015 17:47:46 +0000 (UTC)
From: "Ashish Singhi (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12779355.1425467541000.237892.1441216066938@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=14727718#comment-14727718 ] 

Ashish Singhi commented on HBASE-13153:
---------------------------------------

bq. Is it possible to store cluster Ids as metadata in bulk loaded HFiles ?
Yes, we can do that. We are thinking of that as a last option as we are trying to avoid to write to a hfile as much as possible.

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