hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: HBASE-4089 & HBASE-4147 - on the topic of ops output
Date Fri, 29 Jul 2011 16:50:05 GMT
Can you cast some of these new attributes as metrics (This won't work
for the per-table/per-cf attributes).  Print to log could work.  Here
we json compound info like this when we stick it in log.  Maybe here
too?  Would be nice if an API call too... or add the data to
ClusterStatus fat report object.  Then it could be seen over in shell,


On Fri, Jul 29, 2011 at 4:15 AM, Doug Meil
<doug.meil@explorysmedical.com> wrote:
> Hi Folks-
> You probably already my email yesterday on this...
>   https://issues.apache.org/jira/browse/HBASE-4089 (block cache report)
> ...and I just created this one...
>   https://issues.apache.org/jira/browse/HBASE-4147 (StoreFile query
> report)
> What I'd like to run past the dev-list is this:  if Hbase had periodic
> summary usage statistics, where should they go?  What I'd like to throw
> out for discussion is that I'm suggesting that it should simply go to the
> log files and users can slice and dice this on their own.  No UI (I.e.,
> JSPs), no JMX, etc.
> The summary out the output is this:
> BlockCacheReport:  on configured interval, print out summary of blockcache
> (at table/CF level) to log file. This one is point-in-time, not delta.
> StoreFile read report:  on configured interval, print out summary of
> StoreFile accesses and how much time was spent reading each StoreFile to
> log file.
> Thoughts?
> Doug

View raw message