[
https://issues.apache.org/jira/browse/HBASE-2888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935281#action_12935281
]
Lars George commented on HBASE-2888:
------------------------------------
I think what 3. is for is what we once had as the Historian. Is there a plan to
bring that back and even extend on it?
I agree with Alex though and agreed to help to add this as necessary and
reasonable. We need for users to be able to easily see the status of a
server/table/region etc. since digging in logs is black art and with changing
versions and therefore changing log statements even simple grep scripts may
fail on newer versions. If we had a simple history per table or region of what
happened when (like last compaction, what type was it, how was it triggered?
Same for last flush and splits) I am sure it would help a lot of users. Maybe a
simple event based WAL that is written per RS and that can be displayed nicely
in the UI and maybe even being to clear it should help a lot. Maybe keep the
last N records/events as per a config key?
> 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.
