[HBASE-22106] Log cause of the failure when coprocessor specification parsing fails.

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.4.9
• Fix Version/s: 1.4.10, 1.3.4
• Component/s: logging
• Hadoop Flags: Reviewed
• Assignee: Ankit Singhal
• Reporter: Ankit Singhal
• Created: 25/Mar/19 21:53
• Updated: 07/Oct/19 18:39
• Resolved: 10/Apr/19 17:49

Description

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|
 

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