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

Posted to notifications@accumulo.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2014/04/22 20:30:16 UTC

[jira] [Updated] (ACCUMULO-419) cannot unwatch zookeeper nodes

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

Mike Drob updated ACCUMULO-419:
-------------------------------

    Description: After running randomwalk test for several days, tablet servers began to run out of memory.  Heap dump analysis revealed a large number of HashMap entries.  Inspection of those entries found they were referenced by zookeeper watches.  A quick search finds this to be a known zookeeper issue: ZOOKEEPER-442  (was: After running randomwalk test for several days, tablet servers began to run out of memory.  Heap dump analysis revealed a large number of HashMap entries.  Inspection of those entries found they were referenced by zookeeper watches.  A quick search finds this to be a known zookeeper issue: https://issues.apache.org/jira/browse/ZOOKEEPER-442)

> cannot unwatch zookeeper nodes
> ------------------------------
>
>                 Key: ACCUMULO-419
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-419
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>    Affects Versions: 1.4.0
>            Reporter: Eric Newton
>              Labels: 14_qa_bug
>
> After running randomwalk test for several days, tablet servers began to run out of memory.  Heap dump analysis revealed a large number of HashMap entries.  Inspection of those entries found they were referenced by zookeeper watches.  A quick search finds this to be a known zookeeper issue: ZOOKEEPER-442



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