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

Damien Diederen commented on ZOOKEEPER-4332:
--------------------------------------------

Hi Emil,

bq. However, my current problem is to clean up this state. I cannot do anything 
with this path as I explained.
Right; understood.

bq. Thus, 
"/rmstore/ZKRMStateRoot/RMAppRoot/application_1592399466874_18251/appattempt_159239946687417986_000002"
 should be the longest. The length in bytes should be 10601166.

Okay.

bq. The extra dot is just my editorial mistake in the post, in zoo.cfg it is 
specified as expected: "jute.maxbuffer=4194304".

Okay—just making sure. But that still tells us something: the error you are 
experiencing is happening on the client side \(you are using {{zkCli.sh}}, 
aren't you?), but {{zoo.cfg}} is the server configuration\!

The easiest way to change *its* buffer size is, as far as I know, the 
{{CLIENT_JVMFLAGS}} environment variable. Could you try with something like 
this:

{code:bash}
CLIENT_JVMFLAGS='-Djute.maxbuffer=0x1000000'

export CLIENT_JVMFLAGS

zkCli.sh -server ${MY_CONN_STRING?}
{code}

HTH, \-D


> Cannot access children of znode that owns too many znodes
> ---------------------------------------------------------
>
>                 Key: ZOOKEEPER-4332
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4332
>             Project: ZooKeeper
>          Issue Type: Bug
>          Components: server
>    Affects Versions: 3.6.1
>            Reporter: Emil Kleszcz
>            Priority: Critical
>              Labels: zookeeper
>         Attachments: Screen Shot 2021-06-30 at 16.52.17.png, Screen Shot 
> 2021-06-30 at 16.52.42.png, Screen Shot 2021-06-30 at 16.53.04.png
>
>
> We experience problems with performing any operation (deleteall, get etc.) on 
> a znode that has too many child nodes. In our case, it's above 200k. At the 
> same time jute.max.buffer is 4194304. Increasing it by a few factors doesn't 
> help. This should be either solved by limiting the number of direct znodes 
> allowed by a parameter or by adding a hard limit by default.
> I am attaching some screenshots of the commands and their results. What's 
> interesting the numbers from getAllChildrenNumber and stat (numChildren) 
> commands don't match.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to