[
https://issues.apache.org/jira/browse/HBASE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12934763#action_12934763
]
Alex Baranau commented on HBASE-2888:
-------------------------------------
As per small discussion here: http://search-hadoop.com/m/DZcdNHsTOe2, here are
some extra things we might want to expose:
1. Splits stats.
We have in JMX flush and compaction data (time spent and data amount). Should
we add also stats for split procedures as they affect hbase behaviour too?
2. Flush/Compaction/Split rate.
For flush and compaction we expose only time spent and data amount stats, but
we might also want to show smth like operations "rate" (number of actions).
Based on flush/compaction/split rate one can make judgements on whether some
configuration is properly set (e.g. hbase.hregion.memstore.flush.size).
3. Events log.
Also I think would be very useful for ops to have ability to watch at events
(like splits, flushes, compactions) on a web interface/in JMX, know when they
appear, aka events' log. Thus one can go to to web page and see what can affect
performance degradation for a particular period of time. Currently we have to
(and do) go to log files for that kind of info.
> Review all our metrics
> ----------------------
>
> Key: HBASE-2888
> URL: https://issues.apache.org/jira/browse/HBASE-2888
> Project: HBase
> Issue Type: Improvement
> Components: master
> Reporter: Jean-Daniel Cryans
> Fix For: 0.92.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
