[
https://issues.apache.org/jira/browse/HBASE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935433#action_12935433
]
stack commented on HBASE-2888:
------------------------------
Yeah. Sounds like the 'historian'. The historian was a nice feature but being
a column family on .META. it got in the way of normal operation; clients in
regionservers wanting to log events would get hung up blocking if meta moved or
was unavailable or just get in the way of recovery. A UI could look at the
historian table. We could put in events in reverse order so latest showed
first. It also couldn't record all events IIRC. We could do historian event
logging into a table apart from .META. That might work. Would need to make it
so client could ride unavailability of the historian table or just drop events
if couldn't add an event. That'd be hardest part I'd imagine. We might look
at rowlog to do this? Or we could just emit the events and let another system
render them (tsdb?).
> 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.
