Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 10 Nov 2015 17:54:11 +0000 (UTC)
From: "Lars Hofhansl (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12911916.1447177992000.29774.1447178051099@Atlassian.JIRA>
In-Reply-To: <JIRA.12911916.1447177992000@Atlassian.JIRA>
References: <JIRA.12911916.1447177992000@Atlassian.JIRA>
 <JIRA.12911916.1447177992506@arcas>
Subject: [jira] [Created] (HBASE-14791) [0.98] CopyTable is extremely slow
 when moving delete markers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Lars Hofhansl created HBASE-14791:
-------------------------------------

             Summary: [0.98] CopyTable is extremely slow when moving delete markers
                 Key: HBASE-14791
                 URL: https://issues.apache.org/jira/browse/HBASE-14791
             Project: HBase
          Issue Type: Bug
    Affects Versions: 0.98.16
            Reporter: Lars Hofhansl


We found that some of our copy table job run for many hours, even when there isn't that much data to copy.

[~vik.karma] did his magic and found that the issue with copying delete markers (we use raw mode to also move deletes across).
Looking at the code in 0.98 it's immediately obvious that deletes (unlike puts) are not batched and hence sent to the other side one by one, cause a network RTT for each delete marker.

Looks like in trunk it's doing the right thing (using BufferedMutators for all mutations in TableOutputFormat). So likely only a 0.98 (and 1.0, 1.1, 1.2?) issue.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)