Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of lars.george@gmail.com
 designates 209.85.214.41 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1278)
Subject: Re: Exposing config properties via JMX?
From: Lars George <lars.george@gmail.com>
In-Reply-To: <1338319888.17379.YahooMailNeo@web130101.mail.mud.yahoo.com>
Date: Fri, 1 Jun 2012 16:14:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <F27A4CAC-B9E8-4D6F-8991-F968CDA3DF0C@gmail.com>
References: <1338310343.17943.YahooMailNeo@web130105.mail.mud.yahoo.com>
 <CAKYwJ9ygUrmtqj0eYy8LSi2stGcPs3RjyKRpAYKD4KPtw7uskg@mail.gmail.com>
 <1338319888.17379.YahooMailNeo@web130101.mail.mud.yahoo.com>
To: dev@hbase.apache.org,
 Otis Gospodnetic <otis_gospodnetic@yahoo.com>

Thanks Otis, I also like this idea, as it comes up from time to time. =
Will you also be at the BBuzz HBase workshop on Wednesday? I would love =
to talk JMX and metrics with you (and Alex, who I know is coming).

Lars

On May 29, 2012, at 9:31 PM, Otis Gospodnetic wrote:

> Done. https://issues.apache.org/jira/browse/HBASE-6125
> =20
> Otis
> ----
> Performance Monitoring for Solr / ElasticSearch / HBase - =
http://sematext.com/spm=20
>=20
>=20
>=20
>> ________________________________
>> From: Elliott Clark <eclark@stumbleupon.com>
>> To: dev@hbase.apache.org; Otis Gospodnetic =
<otis_gospodnetic@yahoo.com>=20
>> Sent: Tuesday, May 29, 2012 1:20 PM
>> Subject: Re: Exposing config properties via JMX?
>>=20
>> Yes that would be useful for lots of people.  Can you file a jira ?
>>=20
>> On Tue, May 29, 2012 at 9:52 AM, Otis Gospodnetic <
>> otis_gospodnetic@yahoo.com> wrote:
>>=20
>>> Hi,
>>>=20
>>> For our HBase Performance Monitoring tool we had to do some bytecode
>>> instrumentation to catch the following 2 properties in order to be =
able to
>>> graph them on our MemStore graphs:
>>>=20
>>> * hbase.regionserver.global.memstore.upperLimit
>>> * hbase.regionserver.global.memstore.lowerLimit
>>>=20
>>> Would it make sense to expose these (and all other?) HBase config
>>> properties via JMX, so one can understand how HBase was configured =
by
>>> looking at JMX?  Or are a number of other config properties already =
there
>>> and we'd just need to provide a patch for any missing ones?
>>>=20
>>> Thanks,
>>> Otis
>>> ----
>>> Performance Monitoring for Solr / ElasticSearch / HBase -
>>> http://sematext.com/spm
>>>=20
>>=20
>>=20