t; > Wei
> >
> >
> >
> > From: Gary Helmling
> > To: user@hbase.apache.org,
> > Date: 10/22/2013 07:37 PM
> > Subject:Re: coprocessor status query
> >
> >
> >
> >>
> >> "The coprocessor clas
You are welcome to not use coprocessors.
> IMHO, the current implementation is DOA, primarily because it runs in the
> same JVM as the RS.
> (I'll have to see if I can open a JIRA and make comments.)
>
>
There has been a JIRA for out of process coprocessors for quite some time:
https://issues.apa
e.apache.org,
> Date: 10/22/2013 07:37 PM
> Subject:Re: coprocessor status query
>
>
>
>>
>> "The coprocessor class is of course still in memory on the
>> regionserver,"
>>
>> That was kinda my point.
>>
>> You
@hbase.apache.org,
Date: 10/22/2013 07:37 PM
Subject:Re: coprocessor status query
>
> "The coprocessor class is of course still in memory on the
> regionserver,"
>
> That was kinda my point.
>
> You can't remove the class from the RS until you do a
>
> "The coprocessor class is of course still in memory on the
> regionserver,"
>
> That was kinda my point.
>
> You can't remove the class from the RS until you do a rolling restart.
>
Yes, understood.
However, your original statement that "You can't remove a coprocessor"
needed some clarifi
Gary,
"The coprocessor class is of course still in memory on the regionserver,"
That was kinda my point.
You can't remove the class from the RS until you do a rolling restart.
And to your point... yeah I can see issues in trying to debug failures when you
have failures that are data dep
Unfortunately, the per-region coprocessor list was dropped from HServerLoad
in HBASE-5258. This doesn't leave any easy way for a client to list the
loaded coprocessors on a per-region basis, that I'm aware of.
If you feel like this would be useful to provide, please open a JIRA
describing what yo
Hi Gary, thanks!
It seems that the region observer been removed behavior, is per region and
NOT per coprocessor. So do I have to query each region to get the per
region health status? Or, is there a table level API telling me something
like, I have 10 regions and an observer has been removed in 2
> You can't remove a coprocessor.
>
> Well, you can, but that would require a rolling restart.
>
> It still exists and is still loaded.
>
>
Assuming we are talking about RegionObserver coprocessors here, when a
coprocessor throws an exception (other than IOException), it is either:
a) removed from
Uhm...
You can't remove a coprocessor.
Well, you can, but that would require a rolling restart.
It still exists and is still loaded.
On Oct 21, 2013, at 4:41 PM, Wei Tan wrote:
> Hello, I want to check the status of each coprocessor, in a given table.
> Let's say I have 3 CPs and one of
For #1, the coprocessors reported are live ones.
See CoprocessorHost#getCoprocessors()
For #2, I don't know such API (without parsing ServerLoad) exists.
Cheers
On Mon, Oct 21, 2013 at 2:50 PM, Ted Yu wrote:
> w.r.t. #3, there is a config parameter: "hbase.coprocessor.abortonerror"
> which de
w.r.t. #3, there is a config parameter: "hbase.coprocessor.abortonerror"
which determines whether the hosting server should abort.
See the following tests for examples:
hbase-server/src/test/java/org/apache/hadoop/hbase/coprocessor/TestMasterCoprocessorExceptionWithAbort.java
hbase-server/src/test
Hello, I want to check the status of each coprocessor, in a given table.
Let's say I have 3 CPs and one of them is removed due to some unhandled
exception, so I want to see this status (3 deployed, 2 currently alive).
I found this from
http://blogs.apache.org/hbase/entry/coprocessor_introductio
13 matches
Mail list logo
