You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Yong Zhang (JIRA)" <ji...@apache.org> on 2016/05/10 02:59:12 UTC
[jira] [Updated] (ZOOKEEPER-2426) Remove jute.maxbuffer limit
packetLen in client side
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yong Zhang updated ZOOKEEPER-2426:
----------------------------------
Attachment: ZOOKEEPER-2426.001.patch
First patch, please help to review
> Remove jute.maxbuffer limit packetLen in client side
> ----------------------------------------------------
>
> Key: ZOOKEEPER-2426
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2426
> Project: ZooKeeper
> Issue Type: Improvement
> Affects Versions: 3.5.1
> Reporter: Yong Zhang
> Attachments: ZOOKEEPER-2426.001.patch
>
>
> jute.maxbuffer can be configured in both client and server side, if we try to getChildren from a parent znode with large number of children znode, client may failed to get because of packetLen is more than jute.maxbuffer configured.
> even if we can change the value in java system property, but we have to restart the application, and more all data has been in zookeeper client, check the length/size is unnecessary.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)