[
https://issues.apache.org/jira/browse/HBASE-17817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steen Manniche updated HBASE-17817:
-----------------------------------
Description:
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.
was:
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.
> 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)
