[
https://issues.apache.org/jira/browse/HBASE-10119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845827#comment-13845827
]
Hudson commented on HBASE-10119:
--------------------------------
SUCCESS: Integrated in HBase-TRUNK-on-Hadoop-1.1 #4 (See
[https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-1.1/4/])
HBASE-10119. Allow HBase coprocessors to clean up when they fail (Benoit
Sigoure) (apurtell: rev 1549974)
*
/hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/coprocessor/CoprocessorHost.java
> Allow HBase coprocessors to clean up when they fail
> ---------------------------------------------------
>
> Key: HBASE-10119
> URL: https://issues.apache.org/jira/browse/HBASE-10119
> Project: HBase
> Issue Type: New Feature
> Affects Versions: 0.96.0
> Reporter: Benoit Sigoure
> Assignee: Benoit Sigoure
> Fix For: 0.98.0, 0.96.1, 0.94.15, 0.99.0
>
> Attachments: HBASE-10119-0.94.patch, HBASE-10119.patch
>
>
> In the thread [Giving a chance to buggy coprocessors to clean
> up|http://osdir.com/ml/general/2013-12/msg17334.html] I brought up the issue
> that coprocessors currently don't have a chance to release their own
> resources (be they internal resources within the JVM, or external resources
> elsewhere) when they get forcefully removed due to an uncaught exception
> escaping.
> It would be nice to fix that, either by adding an API called by the
> {{CoprocessorHost}} when killing a faulty coprocessor, or by guaranteeing
> that the coprocessor's {{stop()}} method will be invoked then.
> This feature request is actually pretty important due to bug HBASE-9046,
> which means that it's not possible to properly clean up a coprocessor without
> restarting the RegionServer (!!).
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
