Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
From: Doug Meil <doug.meil@explorysmedical.com>
To: "dev@hbase.apache.org" <dev@hbase.apache.org>
Date: Fri, 29 Jul 2011 07:15:00 -0400
Subject: HBASE-4089 & HBASE-4147 - on the topic of ops output
Thread-Topic: HBASE-4089 & HBASE-4147 - on the topic of ops output
Thread-Index: AcxN4DoUI468Zz/YSM6yMmSgwpMQAQ==
Message-ID: <CA580CF4.B084%doug.meil@explorysmedical.com>
In-Reply-To: <CA575578.B03C%doug.meil@explorysmedical.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.12.0.110505
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0


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. =20

Thoughts?

Doug

>