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-3869) RegionServer metrics - add read and write byte-transfer statistics
Date Mon, 10 Sep 2012 22:18:08 GMT

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

Lars Hofhansl commented on HBASE-3869:

There is a global metric that accumulates the size of all KVs read by a region server, so
it's not what you meant, I guess.
> RegionServer metrics - add read and write byte-transfer statistics
> ------------------------------------------------------------------
>                 Key: HBASE-3869
>                 URL: https://issues.apache.org/jira/browse/HBASE-3869
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Doug Meil
>            Priority: Minor
> It would be beneficial to have the "data transfer weight" of reads and writes per region
> HBASE-3647 split out the read/write metric requests from the uber-"request" metric -
which is great.
> But there isn't a notion of "data transfer weight" and this is why it's important:  the
read metrics are effectively RPC-based.  Thus, with a scan caching of 500, there is 1 RPC
call every 500 rows read (and 1 'read' metric increment).  And this metric doesn't indicate
how much data is being transferred (e.g., a read with 50 attributes will probably cost a lot
more than a read with 5 attributes).

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

View raw message