hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "chunhui shen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-6870) HTable#coprocessorExec always scan the whole table
Date Tue, 25 Sep 2012 04:04:07 GMT

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

chunhui shen updated HBASE-6870:
--------------------------------

    Attachment: HBASE-6870-testPerformance.patch

Run the testPerformance on my local PC:

Before:##Finished testAggregatePerformance, took time:7963ms ##

After:##Finished testAggregatePerformance, took time:672ms ##

In the test, I only create 64 regions for the table, if the region is much more, the result
difference will more bigger
                
> HTable#coprocessorExec always scan the whole table 
> ---------------------------------------------------
>
>                 Key: HBASE-6870
>                 URL: https://issues.apache.org/jira/browse/HBASE-6870
>             Project: HBase
>          Issue Type: Improvement
>          Components: Coprocessors
>    Affects Versions: 0.94.1
>            Reporter: chunhui shen
>            Assignee: chunhui shen
>         Attachments: HBASE-6870.patch, HBASE-6870-testPerformance.patch, HBASE-6870v2.patch,
HBASE-6870v3.patch
>
>
> In current logic, HTable#coprocessorExec always scan the whole table, its efficiency
is low and will affect the Regionserver carrying .META. under large coprocessorExec requests

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message