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 Mon, 27 Mar 2017 07:54:41 GMT

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

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

Not always.  When the Exception is from any CP other than the RegionObserver, it is not really
tied with a Region (And so table).  It might be the Master CPEnvironment or WAL or RS.   When
it is RegionCoprocessorEnvironment, u can get the table name.

> 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}}.
> 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