Re: Coprocessor exception in ResionServer log

2016-10-10 Thread Ted Yu
Can you outline the steps taken in hbase shell ? If you can show skeleton of your endpoint, that may help as well. Lastly, consider upgrading :-) Cheers > On Oct 10, 2016, at 8:54 PM, big data wrote: > > I use the static load method, it seems ok... > > why it can

Re: Coprocessor exception in ResionServer log

2016-10-10 Thread big data
I use the static load method, it seems ok... why it can not running in dynamic load method? 在 16/10/11 上午10:18, big data 写道: > No, it is the original log from hbase, no missing. > > I'll try it through hbase-site.xml. > > thanks > > > > 在 16/10/11 上午10:05, Ted Yu 写道: >> bq. have different

Re: Coprocessor exception in ResionServer log

2016-10-10 Thread big data
No, it is the original log from hbase, no missing. I'll try it through hbase-site.xml. thanks 在 16/10/11 上午10:05, Ted Yu 写道: > bq. have different Class objects for the type otobuf/Service > > Was the above copied verbatim ? > > I wonder why protobuf was cut off. > > If you deploy through

Re: Coprocessor exception in ResionServer log

2016-10-10 Thread Ted Yu
bq. have different Class objects for the type otobuf/Service Was the above copied verbatim ? I wonder why protobuf was cut off. If you deploy through hbase.coprocessor.region.classes in hbase-site.xml, do you still have the same error ? Cheers On Mon, Oct 10, 2016 at 6:43 PM, big data

Re: Coprocessor exception in ResionServer log

2016-10-10 Thread Ted Yu
Could be related to incompatible protobuf versions. What's the output of: mvn dependency:tree Please pastebin it - it should be fairly long. On Mon, Oct 10, 2016 at 6:29 PM, big data wrote: > Dear all, > > I've created an Endpoint coprocessor, and deployed it through

Coprocessor exception in ResionServer log

2016-10-10 Thread big data
Dear all, I've created an Endpoint coprocessor, and deployed it through hbase shell. Then when I run client code, when code response = rpcCallback.get(); rpcCallback.get() return null; in the resion server log, i found this exception: 2016-10-10 15:50:07,636 ERROR