[ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15989194#comment-15989194 ]
Hudson commented on HBASE-17817: -------------------------------- SUCCESS: Integrated in Jenkins build HBase-1.3-IT #34 (See [https://builds.apache.org/job/HBase-1.3-IT/34/]) HBASE-17817 add table name to output (if available) when removing (busbey: rev e4c8a858b1957ab1123d0daf5a21507c7737f519) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java > Make Regionservers log which tables it removed coprocessors from when aborting > ------------------------------------------------------------------------------ > > Key: HBASE-17817 > URL: https://issues.apache.org/jira/browse/HBASE-17817 > Project: HBase > Issue Type: Improvement > Components: Coprocessors, regionserver > Affects Versions: 1.1.2 > Reporter: Steen Manniche > Assignee: Steen Manniche > Labels: logging > Fix For: 2.0.0, 1.4.0, 1.2.6, 1.3.2, 1.1.11 > > Attachments: HBASE-17817.master.001.patch, > HBASE-17817.master.002.patch, HBASE-17817.master.003.patch, > HBASE-17817.master.004.patch > > > When a coprocessor throws a runtime exception (e.g. NPE), the regionserver > handles this according to {{hbase.coprocessor.abortonerror}}. > If the coprocessor was loaded on a specific table, the output in the logs > give no indication as to which table the coprocessor was removed from (or > which version, or jarfile is the culprit). This causes longer debugging and > recovery times. -- This message was sent by Atlassian JIRA (v6.3.15#6346)