hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anoop Sam John (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-17817) Make Regionservers log which tables it removed coprocessors from when aborting
Date Fri, 24 Mar 2017 06:26:41 GMT

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

Anoop Sam John commented on HBASE-17817:
----------------------------------------

When it is Exceptions from RegionObserver CPs, we can say the table info also. But we do have
WALObserver, MasterObserver etc which is not really tied with tables.  Ya it will be better
to say the table info when get Exceptions from region level CPs

> 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
>
> When a coprocessor throws a runtime exception (e.g. NPE), the regionserver handles this
according to {{hbase.coprocessor.abortonerror}}.
> 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