Coprocessor deployment: does jar replacement take effect without restarting hbase?

Question

Assume this case.

I have a coprocessor declared in hbase-site.xml

<property>
<name>hbase.coprocessor.region.classes</name>
<value>my.co.processor</value>
<property>

and in hbase-env.sh I declared a coprocessor class path like this

export HBASE_CLASSPATH="${HBASE_HOME}/lib/coprocessor.jar"

• If I find an error in this coprocessor later, can I just replace this jar file on all area servers without rebooting the entire hbase?

• If I want to add another coprocessor, I think I need to restart all of Hbase, am I right? I know that I can declare hbase for each individual table in the shell, but I think that it’s not an option to think about whether I have many tables to use the new coprocessor.

Answer 1

HTable: hTableDescriptor.addCoprocessor(className, , .PRIORITY_USER, null); , , .

Answer 2

jar , . , . , ; hbase .