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

Andrew Purtell commented on HBASE-11096:
----------------------------------------

I applied patch v3 to trunk and ran the coprocessor unit tests locally. The new 
test TestCoprocessorStop failed:
{quote}
Test set: org.apache.hadoop.hbase.coprocessor.TestCoprocessorStop
-------------------------------------------------------------------------------
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 29.904 sec <<< 
FAILURE!
testStopped(org.apache.hadoop.hbase.coprocessor.TestCoprocessorStop)  Time 
elapsed: 1.326 sec  <<< FAILURE!
java.lang.AssertionError: Master flag file should have been created
        at org.junit.Assert.fail(Assert.java:88)
        at org.junit.Assert.assertTrue(Assert.java:41)
        at 
org.apache.hadoop.hbase.coprocessor.TestCoprocessorStop.testStopped(TestCoprocessorStop.java:120)
{quote}

> stop method of Master and RegionServer coprocessor  is not invoked
> ------------------------------------------------------------------
>
>                 Key: HBASE-11096
>                 URL: https://issues.apache.org/jira/browse/HBASE-11096
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.96.2, 0.98.1, 0.94.19
>            Reporter: Qiang Tian
>            Assignee: Qiang Tian
>             Fix For: 0.99.0, 0.96.3, 0.94.20, 0.98.3
>
>         Attachments: HBASE-11096-0.94.patch, HBASE-11096-0.96.patch, 
> HBASE-11096-0.98.patch, HBASE-11096-trunk-v0.patch, 
> HBASE-11096-trunk-v0.patch, HBASE-11096-trunk-v1.patch, 
> HBASE-11096-trunk-v2.patch, HBASE-11096-trunk-v3.patch
>
>
> the stop method of coprocessor specified by 
> "hbase.coprocessor.master.classes" and  
> "hbase.coprocessor.regionserver.classes"  is not invoked.
> If coprocessor allocates OS resources, it could cause master/regionserver 
> resource leak or hang during exit.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to