Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 8 Jan 2015 08:48:35 +0000 (UTC)
From: "Cosmin Lehene (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12608138.1348003363000.36151.1420706915103@Atlassian.JIRA>
In-Reply-To: <JIRA.12608138.1348003363000@Atlassian.JIRA>
References: <JIRA.12608138.1348003363000@Atlassian.JIRA>
 <JIRA.12608138.1348003363886@arcas>
Subject: [jira] [Commented] (HBASE-6812) Export dry run mode.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Cosmin Lehene commented on HBASE-6812:
--------------------------------------

[~apurtell], [~stack] looks like a nice to have, but not sure how much this is actually used...

> Export dry run mode.
> --------------------
>
>                 Key: HBASE-6812
>                 URL: https://issues.apache.org/jira/browse/HBASE-6812
>             Project: HBase
>          Issue Type: New Feature
>            Reporter: Jonathan Hsieh
>              Labels: delete
>
> We encountered customer experiencing poor performance on Exports and we've spent some time trying to isolate the performance bottlenecks.  It was suggested to add a "dry run mode" that just scans the table but does not emit data to hdfs.  This would be really useful for determining if problems are on the write path or the read path.


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