You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "David Medinets (JIRA)" <ji...@apache.org> on 2014/07/26 00:58:39 UTC

[jira] [Commented] (ACCUMULO-3022) Limit size of data objects in ZooKeeper

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

David Medinets commented on ACCUMULO-3022:
------------------------------------------

Another consideration is that the Zookeeper ensemble can be shared. Therefore, Accumulo could be affected by another application using Zookeeper's memory. If we limit use of Zookeeper memory by Accumulo to enhance stability, then logically we should alert when memory usage goes over some limit. But I suggest that such functionality belongs to a monitoring tool not to Accumulo.

> Limit size of data objects in ZooKeeper
> ---------------------------------------
>
>                 Key: ACCUMULO-3022
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3022
>             Project: Accumulo
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Keith Turner
>            Priority: Minor
>             Fix For: 1.7.0
>
>
> This issue is inspired by ACCUMULO-3021.  The original issue was concerning table names, but I've expanded the issue to include other data objects in ZooKeeper (see comments below), especially in light of the fact that there's already an issue specifically addressing giant table names (ACCUMULO-2366).



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