hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hsieh (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6812) Export dry run mode.
Date Thu, 08 Jan 2015 18:04:35 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Jonathan Hsieh resolved HBASE-6812.
    Resolution: Won't Fix

I filed this way back, closing it.  We could likely do a row counter job to scan all the rows
which would be roughly equivalent and help diagnose the read side.

> 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

View raw message