Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1078)
Subject: Re: JMX bean registrations for Master & RegionServers
From: Paul Smith <psmith@aconex.com>
In-Reply-To: <x2te6aa01cc1004090423l3a0c0579gb7feabde0f517100@mail.gmail.com>
Date: Fri, 9 Apr 2010 22:18:51 +1000
Content-Transfer-Encoding: quoted-printable
Message-Id: <222B5E2B-08BC-496E-A121-73BBF7E4025A@aconex.com>
References: <40A7515D-3575-4819-BCF3-75D30BFC97BA@aconex.com>
 <x2te6aa01cc1004090423l3a0c0579gb7feabde0f517100@mail.gmail.com>
To: hbase-dev@hadoop.apache.org


On 09/04/2010, at 9:23 PM, Gary Helmling wrote:

> Hi Paul,
>=20
> For the master process, you should see 2 MBeans registered (assuming
> distributed setup with default ports):
>=20
> hadoop:name=3DMasterStatistics,service=3DMaster
> hadoop:name=3DRPCStatistics-60000,service=3DHBase
>=20
> The first is master-specific metrics (just cluster request count I =
think?).
> The second is a common RPCStatistics MBean for the master's RPC calls. =
 The
> RPCStatistics MBean will include whatever port is used in the name.
>=20
> For a regionserver, you should see:
>=20
> hadoop:name=3DRegionServerStatistics,service=3DRegionServer
> hadoop:name=3DRPCStatistics-60020,service=3DHBase
>=20

ok, well under my local simple testing (sort of straight out of the box =
unpacking, not distributed), the RegionServer does _not_ export that =
RegionServerStatistics which is interesting.  If it did, that would be =
enough to differentiate it.  Right now, in simple mode, the RS only =
exports the RPCStatistics. (this is for hbase-0.20.3)

Let me dig further, thanks.

thanks,

Paul