Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> coprocessor status query


Copy link to this message
-
Re: coprocessor status query
Hi Gary, thanks for your clarification and yes, I totally agree with your
statement.

The class is not removed but the CP is kind of removed and not active
after an un-handled exception.
I will take a look at the Jira you mentioned.
Best regards,
Wei

From:   Gary Helmling <[EMAIL PROTECTED]>
To:     [EMAIL PROTECTED],
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 rolling restart.
>

Yes, understood.

However, your original statement that "You can't remove a coprocessor"
needed some clarification, in that the coprocessor that threw the
exception
_is_ removed from the active set of coprocessors for that region.  So it
is
no longer invoked for pre/post hooks on the call path for further
requests.

>From the original question, I take it that this invocation context is what
Wei cared about.

NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB