Github user linzhonghong commented on the issue:

    https://github.com/apache/eagle/pull/417
  
    @haoch hi, i find the coprocessor exception here: 
https://issues.apache.org/jira/browse/EAGLE-520
    i view all commits in this PR, but  i cant not find which commit is to fix 
it? 
    how can i fix this exception? thanks!
    
    ```java
    ABORTING region server sandbox.hortonworks.com,60020,1473225565436: The 
coprocessor 
org.apache.eagle.storage.hbase.query.coprocessor.AggregateProtocolEndPoint 
threw an unexpected exception
    Cause:
    java.lang.LinkageError: loader constraint violation in interface itable 
initialization: when resolving method 
"org.apache.eagle.storage.hbase.query.coprocessor.AggregateProtocolEndPoint.getService()Lcom/google/protobuf/Service;"
 the class loader (instance of 
org/apache/hadoop/hbase/util/CoprocessorClassLoader) of the current class, 
org/apache/eagle/storage/hbase/query/coprocessor/AggregateProtocolEndPoint, and 
the class loader (instance of sun/misc/Launcher$AppClassLoader) for interface 
org/apache/hadoop/hbase/coprocessor/CoprocessorService have different Class 
objects for the type com/google/protobuf/Service used in the signature
            at java.lang.Class.getDeclaredConstructors0(Native Method)
            at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
            at java.lang.Class.getConstructor0(Class.java:3075)
            at java.lang.Class.newInstance(Class.java:412)
            at 
org.apache.hadoop.hbase.coprocessor.CoprocessorHost.loadInstance(CoprocessorHost.java:247)
            at 
org.apache.hadoop.hbase.coprocessor.CoprocessorHost.load(CoprocessorHost.java:210)
            at 
org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.loadTableCoprocessors(RegionCoprocessorHost.java:301)
            at 
org.apache.hadoop.hbase.regionserver.RegionCoprocessorHost.<init>(RegionCoprocessorHost.java:200)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.<init>(HRegion.java:701)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.<init>(HRegion.java:608)
            at sun.reflect.GeneratedConstructorAccessor70.newInstance(Unknown 
Source)
            at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
            at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.newHRegion(HRegion.java:5438)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:5749)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:5722)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:5678)
            at 
org.apache.hadoop.hbase.regionserver.HRegion.openHRegion(HRegion.java:5629)
            at 
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.openRegion(OpenRegionHandler.java:465)
            at 
org.apache.hadoop.hbase.regionserver.handler.OpenRegionHandler.process(OpenRegionHandler.java:139)
            at 
org.apache.hadoop.hbase.executor.EventHandler.run(EventHandler.java:128)
            at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
            at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
            at java.lang.Thread.run(Thread.java:745)
    ```


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to