You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2014/02/22 02:24:22 UTC

[jira] [Commented] (HBASE-8402) ScanMetrics depends on number of rpc calls to the server.

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

Hudson commented on HBASE-8402:
-------------------------------

SUCCESS: Integrated in HBase-0.94-security #419 (See [https://builds.apache.org/job/HBase-0.94-security/419/])
HBASE-10583 backport HBASE-8402 to 0.94 - ScanMetrics depends on number of rpc calls to the server. (Liu Shaohui and Himanshu Vashishtha) (larsh: rev 1570756)
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/ClientScanner.java
* /hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/client/TestFromClientSide.java


> ScanMetrics depends on number of rpc calls to the server.
> ---------------------------------------------------------
>
>                 Key: HBASE-8402
>                 URL: https://issues.apache.org/jira/browse/HBASE-8402
>             Project: HBase
>          Issue Type: Bug
>          Components: Client, metrics
>    Affects Versions: 0.95.0
>            Reporter: Himanshu Vashishtha
>            Assignee: Himanshu Vashishtha
>            Priority: Minor
>             Fix For: 0.98.0, 0.95.1
>
>         Attachments: HBASE-8402-v1.patch, HBASE-8402-v2.patch
>
>
> Currently, scan metrics is not published in case there is one trip to server. I was testing it on a small row range (200 rows) with a large cache value (1000). It doesn't look right as metrics should not depend on number of rpc calls (number of rpc call is just one metrics fwiw).



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)