[
https://issues.apache.org/jira/browse/ZOOKEEPER-2430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15294867#comment-15294867
]
Hadoop QA commented on ZOOKEEPER-2430:
--------------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12805417/ZOOKEEPER-2430.001.patch
against trunk revision 1743978.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-ZOOKEEPER-Build/3166//console
This message is automatically generated.
> Remove jute.maxbuffer limit packetLen in client side
> ----------------------------------------------------
>
> Key: ZOOKEEPER-2430
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2430
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Yong Zhang
> Attachments: ZOOKEEPER-2430.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)
