hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steen Manniche (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
Date Tue, 11 Apr 2017 17:02:42 GMT

    [ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15964643#comment-15964643
] 

Steen Manniche commented on HBASE-17817:
----------------------------------------

Thank you for the elaborate comments. As per your suggestion on hbase-user, I created a review-board
issue and continued the development of the patch there.

With regards to the {{isAssignableFrom}} comment: you are absolutely right, and I will make
that part of the patch.

> 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
>              Labels: logging
>         Attachments: HBASE-17817.master.001.patch, HBASE-17817.master.002.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)

Mime
View raw message