Thanks Himanshu and Gary for the quick reply. After adding the coprocessor class in hbase-site.xml it worked fine. Actually, i was aware that my coprocessor is not being loaded into region; hence the exception. But i was expecting the co-processor to be loaded since i was setting the conf in my code. Does this mean that "hbase.coprocessor.region.classes" is not a client side configuration? I am just curious to know why it was not working when i was setting the conf through code.
Thanks, Anil Gupta On Mon, May 7, 2012 at 2:00 PM, Gary Helmling <[email protected]> wrote: > > > > org.apache.hadoop.hbase.ipc.HBaseRPC$UnknownProtocolException: > > org.apache.hadoop.hbase.ipc.HBaseRPC$UnknownProtocolException: No > matching > > handler for protocol > org.apache.hadoop.hbase.coprocessor.AggregateProtocol > > in region transactions,,1335223974116.e9190687f8a74b5083b39b6e5bd55705. > > The exception indicates that the AggregateImplementation coprocessor > is not loaded on your region servers. Setting > "hbase.coprocessor.region.classes" in the client configuration that > you use is not sufficient. You need to either set this in the > hbase-site.xml file used by your region servers (and restart the > region servers), or you can enable the coprocessor for a specific > table by disabling the table, setting a property on the > HTableDescriptor and re-enabling the table. > > For more details, see > > http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/coprocessor/package-summary.html#package_description > -- Thanks & Regards, Anil Gupta
