Ankit Singhal created HBASE-22106:
-------------------------------------

             Summary: Log cause of the failure when coprocessor specification 
parsing fails.
                 Key: HBASE-22106
                 URL: https://issues.apache.org/jira/browse/HBASE-22106
             Project: HBase
          Issue Type: Bug
          Components: logging
    Affects Versions: 1.4.9
            Reporter: Ankit Singhal
            Assignee: Ankit Singhal


 {code}
2019-02-15 22:56:33,008 ERROR [RS_OPEN_REGION-n79:16020-16] 
regionserver.RegionCoprocessorHost: Malformed table coprocessor specification: 
key=coprocessor$2, spec: 
|org.apache.phoenix.coprocessor.UngroupedAggregateRegionObserver|805306366|
2019-02-16 00:39:33,651 ERROR [RS_OPEN_REGION-n76:16020-14] 
regionserver.RegionCoprocessorHost: Malformed table coprocessor specification: 
key=coprocessor$1, spec: 
|org.apache.phoenix.coprocessor.ScanRegionObserver|805306366|
2019-02-16 00:39:33,651 ERROR [RS_OPEN_REGION-n76:16020-19] 
regionserver.RegionCoprocessorHost: Malformed table coprocessor specification: 
key=coprocessor$1, spec: 
|org.apache.phoenix.coprocessor.ScanRegionObserver|805306366|
 {code}

I checked the same coprocessor specification(logged in exception) with the code 
and it is parsed successfully. And even after the restart , regionserver also 
didn't complain about it.

I think we should be logging the cause of the exception while parsing table 
descriptor for the coprocessor for better debugging.

https://github.com/apache/hbase/blob/branch-1.4/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RegionCoprocessorHost.java#L318



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to