Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (athena.apache.org: domain of michael_segel@hotmail.com
 designates 65.55.111.162 as permitted sender)
Message-ID: <BLU0-SMTP32996A65861E9E34E819FF38F000@phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: cluster monitoring
From: Michael Segel <michael_segel@hotmail.com>
In-Reply-To: 
 <CAOF-KfjA-x0oiQa2MHP69OTUSMJn1OGqnMor3pyHW3ysuiP3KQ@mail.gmail.com>
Date: Tue, 5 Feb 2013 08:16:57 -0600
CC: hbase-user@hadoop.apache.org
Content-Transfer-Encoding: quoted-printable
References: 
 <CAOF-KfjA-x0oiQa2MHP69OTUSMJn1OGqnMor3pyHW3ysuiP3KQ@mail.gmail.com>
To: user@hbase.apache.org

Sounds like you're looking to see what rows are being selected within a =
region.=20

In theory you could do this w coprocessors, but I wouldn't recommend it.=20=

You're going to take a huge performance hit and you'd have a hard time =
justifying it. (IMHO)=20
The problem w a Debug mode is that once you load a coprocessor class, =
you can't drop it.=20


On Feb 5, 2013, at 7:27 AM, Rita <rmorgan466@gmail.com> wrote:

> hi,
>=20
> is it possible to see what keys are being hit throughout the cluster?
> --=20
> --- Get your facts first, then you can distort them as you please.--