You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2017/04/26 22:36:04 UTC

[jira] [Assigned] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting

     [ https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Busbey reassigned HBASE-17817:
-----------------------------------

    Assignee: Steen Manniche

> 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
>         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)