hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (HBASE-10119) Allow HBase coprocessors to clean up when they fail
Date Tue, 10 Dec 2013 21:26:07 GMT

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

Andrew Purtell updated HBASE-10119:

    Comment: was deleted

(was: {color:red}-1 overall{color}.  Here are the results of testing the latest attachment

  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/8125//console

This message is automatically generated.)

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

View raw message