hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Hofhansl (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-10047) postScannerFilterRow consumes a lot of CPU in tall table scans
Date Mon, 23 Dec 2013 01:36:50 GMT

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

Lars Hofhansl commented on HBASE-10047:

You're saying we catch ClassCastException and then remove the coprocessor?
Looking at the code a bit more; in the RegionCoprocessorHost case we add Endpoint to the list
of coprocessors, which does not seem to be necessary. Unfortunately only the tableCoprocessors
are loaded in RegionCoprocessorHost, the systemCoprocessors are loaded in CoprocessorHost.
Could refactor that, or simply just remove the Endpoint from the set of coprocessors, it seems
they need (and should?) not to in there.

> 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: 10047-0.94-poc-v3.txt, 10047-0.94-sample-v2.txt, 10047-0.94-sample.txt,
> 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