You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2012/11/09 17:10:13 UTC

[jira] [Commented] (ACCUMULO-766) master is "leaking" ZooLock objects

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

Hudson commented on ACCUMULO-766:
---------------------------------

Integrated in Accumulo-Trunk #545 (See [https://builds.apache.org/job/Accumulo-Trunk/545/])
    ACCUMULO-766
There is a race condition between checking for a lock
and removing the node that holds the lock.  This causes
a spurious error message in the logs (and monitor). (Revision 1407489)

     Result = SUCCESS
ecn : 
Files : 
* /accumulo/trunk/server/src/main/java/org/apache/accumulo/server/master/LiveTServerSet.java

                
> master is "leaking" ZooLock objects
> -----------------------------------
>
>                 Key: ACCUMULO-766
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-766
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>    Affects Versions: 1.4.1, 1.4.0
>         Environment: discovered on a large cluster
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Blocker
>             Fix For: 1.5.0, 1.4.2
>
>
> Analysing the memory usage of the master, I noticed many ZooLock objects.  1.4e7 of them, in fact.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira