[
https://issues.apache.org/jira/browse/HBASE-11573?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-11573:
--------------------------
Attachment: 11573v2.txt
v2 adds printing out age only if non-zero in UI (some 'blockcaches' will always
be zero).
[~ndimiduk] You good w/ this boss? Age-at-eviction time is more actionable
than what I had previous (age-in-cache). The latter is still there if you JSON
(only generated when report is made) but the focus is put instead on the new
actionable age-at-eviction.
> Report age on eviction
> ----------------------
>
> Key: HBASE-11573
> URL: https://issues.apache.org/jira/browse/HBASE-11573
> Project: HBase
> Issue Type: Sub-task
> Components: BlockCache
> Reporter: stack
> Assignee: stack
> Fix For: 0.99.0, 2.0.0
>
> Attachments: 11573.txt, 11573v2.txt, Screen Shot 2014-07-22 at
> 5.17.27 PM.png
>
>
> From the parent issue, Todd reminds us of the old Jim Gray '5 minute rule' on
> whether to cache.
> In master, we were reporting age only it was the inactionable inverse of 'how
> long blocks are staying in the cache'.
> Let me add to our cache stats a histogram of age on eviction and change the
> UI reporting so it is age at eviction (plus stddev). The JSON version has
> percentiles (and if wanted, the old age report of age of items in cache).
--
This message was sent by Atlassian JIRA
(v6.2#6252)
