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 yuzhihong@gmail.com
 designates 74.125.82.169 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <B8FF8BA8-B499-4E56-B754-A79BD8D4D202@gmail.com>
References: <34BAE961-718E-426F-8B8A-E66F6D0E272C@gmail.com>
	<AD2A835D-22FB-43E8-AC20-A15FB0B5FEED@gmail.com>
	<C0AF0F92-4A83-4DFE-999F-0C442BEACE18@gmail.com>
	<CALte62xSTR0+VpPq1eBCDM9ZAUGN_XSyALQTc3QhU_+y_9iTeQ@mail.gmail.com>
	<CAF1+Vs9rhrpUNe4KFg14N+ruvKWkLgVv3P=cRcJ86pqAW9xF=Q@mail.gmail.com>
	<B8FF8BA8-B499-4E56-B754-A79BD8D4D202@gmail.com>
Date: Mon, 10 Dec 2012 08:03:55 -0800
Message-ID: 
 <CALte62xDrK+jcaC5_86kc__bOwCxBMWoV3yVGnjkQrHk-at4Qg@mail.gmail.com>
Subject: Re: Checking if a coprocessor was loaded successfully from client
From: Ted Yu <yuzhihong@gmail.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=f46d0438904d621ff104d081b6d9

--f46d0438904d621ff104d081b6d9
Content-Type: text/plain; charset=ISO-8859-1

Asaf:
Your coprocessor was successfully running prior to the schema change ?

See HBASE-6873 <https://issues.apache.org/jira/browse/HBASE-6873> Clean up
Coprocessor load failure handling.

Cheers

On Mon, Dec 10, 2012 at 5:11 AM, Mesika, Asaf <asaf.mesika@gmail.com> wrote:

> I guess I'm missing something in the sequence of actions here:
>
> 1. I'm disabling the table. This action is synchronous.
> 2. I'm running the method hBaseAdmin.modifyTable(), which is *asynchronous*
> 3. I'm supposed to use hBaseAdmin.getAlterStatus() to check every x
> seconds whether all regions have been modified.
> 4. Once that has passed, I can finally enable the table, which is a
> synchronous action. This should signify that the table's region are online,
> thus have loaded the region observer class and instantiated it - meaning,
> it has found the JAR file specified in its HDFS location.
>
> hasCoprocessor just checks whether the metadata object has the coprocessor
> attribute and it if has the className you supplied to it.
> How can I know that if a classname is present on a HTableDescriptor, then
> al the tables's regions successfully instantiated the region observer?
>
>
>
> On Dec 10, 2012, at 10:01 AM, anil gupta wrote:
>
> > Hi Asaf,
> >
> > Have a look at the
> > *hasCoprocessor<
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HTableDescriptor.html#hasCoprocessor%28java.lang.String%29
> >
> > * method of HTD:
> >
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HTableDescriptor.html#hasCoprocessor(java.lang.String)
> >
> > It might be helpful for you. I have used it in past to check whether a
> > coprocessors is successfully added or not.
> >
> > HTH,
> > Anil
> >
> > On Sun, Dec 9, 2012 at 2:25 PM, Ted Yu <yuzhihong@gmail.com> wrote:
> >
> >> On region server web UI, you should see the list of coprocessors loaded.
> >>
> >> But I guess you're looking for a programmatic way of detecting
> coprocessor
> >> deployment.
> >>
> >> Cheers
> >>
> >> On Sun, Dec 9, 2012 at 12:29 PM, Mesika, Asaf <asaf.mesika@gmail.com>
> >> wrote:
> >>
> >>> 0.94.0
> >>> On Dec 9, 2012, at 3:03 PM, yuzhihong@gmail.com wrote:
> >>>
> >>>> Which hbase version are you targeting ?
> >>>>
> >>>> Thanks
> >>>>
> >>>>
> >>>>
> >>>> On Dec 9, 2012, at 2:55 AM, "Mesika, Asaf" <asaf.mesika@gmail.com>
> >>> wrote:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> I wrote a custom Region Observer.
> >>>>> I'm currently writing an Installer class for it.
> >>>>> In this installer I'm adding the region observer by adding a
> >>> coprocessor to the HTableDescriptor, and then calling modifyTable by
> >>> HBaseAdmin.
> >>>>>
> >>>>> My question is: How can I check whether region observer was loaded
> >>> successfully for this table?
> >>>>>
> >>>>> I tried searching for a way to get the Coprocessor.State somehow for
> >> my
> >>> region observer so I'll know it's ACTIVE, but couldn't find a way.
> >>>>>
> >>>>>
> >>>>> Thank you,
> >>>>>
> >>>>> Asaf
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>
> >
> >
> >
> > --
> > Thanks & Regards,
> > Anil Gupta
>
>

--f46d0438904d621ff104d081b6d9--