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

Hadoop QA commented on HBASE-4684:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  
http://issues.apache.org/jira/secure/attachment/12502013/HBASE-4684-v2-0.90.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

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

    -1 patch.  The patch command could not apply the patch.

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

This message is automatically generated.
                
> REST server is leaking ZK connections in 0.90
> ---------------------------------------------
>
>                 Key: HBASE-4684
>                 URL: https://issues.apache.org/jira/browse/HBASE-4684
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.90.4
>            Reporter: Jean-Daniel Cryans
>            Assignee: Andrew Purtell
>            Priority: Critical
>             Fix For: 0.90.5
>
>         Attachments: HBASE-4684-0.90.patch, HBASE-4684-v2-0.90.patch
>
>
> As reported a month ago, http://search-hadoop.com/m/FD6gmKzrxY1, the REST 
> server is leak ZK connections. Upon investigation I see that 
> TableResource.scanTransformAttrs creates a new HBA per minute per table (when 
> the server is getting requests) but never deletes the connection created in 
> there.
> There are a bunch of other places where HBAs are created but not cleaned 
> after like SchemaResource, StorageClusterStatusResource, 
> StorageClusterVersionResource, ExistsResource, etc. Those places shouldn't be 
> as leaky under normal circumstances tho.
> Thanks to Jack Levin for bringing up this issue again when he tried to 
> upgrade.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to