maoling opened a new pull request #1129: ZOOKEEPER-3593: fix the default value 
of jute.maxbuffer in client side and an optimization for the documentation
URL: https://github.com/apache/zookeeper/pull/1129
 
 
   - The default value of `jute.maxbuffer` in client side said it's 4MB, but 
actually, it was never working, because when the client reads the deserialized 
znode data, it also calls `checkLength(BinaryInputArchive.java:127)` where  
`jute.maxbuffer` default value is 1MB. It's easy to reproduce, just read a 
znode more than 1MB with any special configure client. Look at the stack trace 
I attached in the JIRA
   - Users also confused about that the doc said `jute.maxbuffer` must be set 
on all servers and clients, but their default value is not same in the 
[ZOOKEEPER-1295](https://issues.apache.org/jira/browse/ZOOKEEPER-1295)
   - more details in the 
[ZOOKEEPER-3593](https://issues.apache.org/jira/browse/ZOOKEEPER-3593)

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to