[
https://issues.apache.org/jira/browse/ZOOKEEPER-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373289#comment-17373289
]
Emil Kleszcz commented on ZOOKEEPER-4332:
-----------------------------------------
Hi Damien,
It worked, indeed I was missing the flag on the client-side! In fact, I had
CLIENT_JVMFLAGS defined in java.env but I was missing there the jute.maxbuffer
flag.
Thank you for your help,
Emil
> 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)
