You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Eric Newton (JIRA)" <ji...@apache.org> on 2014/07/02 17:20:25 UTC

[jira] [Resolved] (ACCUMULO-2757) millions of zookeeper watches

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

Eric Newton resolved ACCUMULO-2757.
-----------------------------------

    Resolution: Later

Shelving this ticket until it's likely to be a real problem in the near future.

> millions of zookeeper watches
> -----------------------------
>
>                 Key: ACCUMULO-2757
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2757
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client, master, tserver
>         Environment: very large clusters
>            Reporter: Eric Newton
>
> I recently learned how to get the number of watches in a zookeeper node.
> {noformat}
> $ echo wchp | nc localhost 2181
> {noformat}
> There are a surprising number of watches supporting table configuration.  A single tserver accumulo instance with one data table is using 872 watches.  Large clusters, even with many zookeepers, can have millions of watches.
> We may need to watch a single notification node, or serialize the table configs into a single node per table.  That would accomplish ACCUMULO-1568, too.



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