hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Liochon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10047) postScannerFilterRow consumes a lot of CPU in tall table scans
Date Wed, 27 Nov 2013 09:11:35 GMT

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

Nicolas Liochon commented on HBASE-10047:

I was thinking about
- allowing the coprocessor to explicitly states the functions it overloaded
- and/or: by reflexivity, check if the method is implemented in the client coprocessor class
or comes from the BaseRegionObserver.

In both cases, we would construct a list of coprocessorWithPostScannerFilterRow when we load
the coprocessor, and we would use this list in the host.

> postScannerFilterRow consumes a lot of CPU in tall table scans
> --------------------------------------------------------------
>                 Key: HBASE-10047
>                 URL: https://issues.apache.org/jira/browse/HBASE-10047
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Lars Hofhansl
>         Attachments: postScannerFilterRow.png
> Continuing my profiling quest, I find that in scanning tall table (and filtering everything
on the server) a quarter of the time is now spent in the postScannerFilterRow coprocessor

This message was sent by Atlassian JIRA

View raw message