Hi Shawn, Thanks for the update.
Yes, I’m facing a situation similar to that described in https://issues.apache.org/jira/browse/ZOOKEEPER-4052. Since this issue remains unresolved, would it be advisable to temporarily set the *jute.maxbuffer* server side slightly lower than the client side, despite the documentation recommending the same setting on both sides? This adjustment might be necessary because the data received by the client is consistently larger than the data stored on the server. Regards, Yifei On Sun, Aug 4, 2024 at 1:29 AM Shawn Heisey <[email protected]> wrote: > On 7/22/2024 10:29, yifei zhang wrote: > > According to the ZooKeeper documentation ( > > https://zookeeper.apache.org/doc/r3.6.4/zookeeperAdmin.html), the > default > > *jute.maxbuffer* in ZooKeeper is 1,048,575 bytes for both the server and > > client sides. However, creating a znode with a size close to this limit > can > > cause issues. > > > > For example, a znode (test_node) with a size of 1,048,494 bytes can be > > created on the ZooKeeper server without any problems. But you will > > encounter an exception if you try to retrieve this znode using the > > ZooKeeper CLI or java client. We saw this issue across four different > > Zookeeper versions: 3.6.4, 3.7.2, 3.8.4, and 3.9.2. > > Here's an issue that is at least related, and something I have run into > using ZK with Solr: > > https://issues.apache.org/jira/browse/ZOOKEEPER-1162 > > This is slightly different than what you've described, I think. That > issue describes a situation where a znode gets to be very large by > adding lots of children to it, and I think you have described a > situation where the data stored in a znode is near the size limit, not > anything to do with child nodes. > > I saw another issue that might be a more exact fit for what you've > described: > > https://issues.apache.org/jira/browse/ZOOKEEPER-4052 > > Thanks, > Shawn > >
