You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Purtell (JIRA)" <ji...@apache.org> on 2014/09/02 18:38:21 UTC

[jira] [Commented] (HBASE-11876) RegionScanner.nextRaw(...) should not update metrics

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

Andrew Purtell commented on HBASE-11876:
----------------------------------------

Sounds good to me. Want to get a patch into .6? I will be tagging the next RC tonight.

> RegionScanner.nextRaw(...) should not update metrics
> ----------------------------------------------------
>
>                 Key: HBASE-11876
>                 URL: https://issues.apache.org/jira/browse/HBASE-11876
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.98.6
>            Reporter: Lars Hofhansl
>
> I added the RegionScanner.nextRaw(...) to allow "smart" client to avoid some of the default work that HBase is doing, such as {start|stop}RegionOperation and synchronized(scanner) for each row.
> Metrics should follow the same approach. Collecting them per row is expensive and a caller should have the option to collect those later or to avoid collecting them completely.
> We can also save some cycles in RSRcpServices.scan(...) if we updated the metric only once/batch instead of each row.



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