Otis Gospodnetic 2012-05-29, 16:52
Elliott Clark 2012-05-29, 17:20
Otis Gospodnetic 2012-05-29, 19:31
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).
On May 29, 2012, at 9:31 PM, Otis Gospodnetic wrote:
> Done. https://issues.apache.org/jira/browse/HBASE-6125
> Performance Monitoring for Solr / ElasticSearch / HBase - http://sematext.com/spm
>> From: Elliott Clark <[EMAIL PROTECTED]>
>> To: [EMAIL PROTECTED]; Otis Gospodnetic <[EMAIL PROTECTED]>
>> Sent: Tuesday, May 29, 2012 1:20 PM
>> Subject: Re: Exposing config properties via JMX?
>> Yes that would be useful for lots of people. Can you file a jira ?
>> On Tue, May 29, 2012 at 9:52 AM, Otis Gospodnetic <
>> [EMAIL PROTECTED]> wrote:
>>> 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:
>>> * hbase.regionserver.global.memstore.upperLimit
>>> * hbase.regionserver.global.memstore.lowerLimit
>>> 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?
>>> Performance Monitoring for Solr / ElasticSearch / HBase -