hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars George (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-2888) Review all our metrics
Date Tue, 26 Jul 2011 12:54:10 GMT

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

Lars George commented on HBASE-2888:
------------------------------------

Another issue I found using the metrics is that all new client API calls are lumping everything
under "multi" (for the RPC calls), for all batchable operations (which are most). This makes
it difficult to track actual get/put/delete calls and their counts. Obviously this is OK in
terms of RPC call counts, but these metrics were useful to see what the request pattern looks
like. Trunk adds read/write counts to the RS metrics, which is good. But maybe we should have
a more detailed count as well? Only if needed.

> Review all our metrics
> ----------------------
>
>                 Key: HBASE-2888
>                 URL: https://issues.apache.org/jira/browse/HBASE-2888
>             Project: HBase
>          Issue Type: Improvement
>          Components: master, metrics
>            Reporter: Jean-Daniel Cryans
>
> HBase publishes a bunch of metrics, some useful some wasteful, that should be improved
to deliver a better ops experience. Examples:
>  - Block cache hit ratio converges at some point and stops moving
>  - fsReadLatency goes down when compactions are running
>  - storefileIndexSizeMB is the exact same number once a system is serving production
load
> We could use new metrics too.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message