[ZOOKEEPER-1295] Documentation for jute.maxbuffer is not correct in ZooKeeper Administrator's Guide

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.2
• Component/s: documentation
• Labels: newbie
• Assignee: Mohammad Arshad
• Reporter: Daniel Lord
• Created: 09/Nov/11 19:23
• Updated: 27/Oct/19 09:28
• Resolved: 28/May/16 17:00

Description

The jute maxbuffer size is documented as being defaulted to 1 megabyte in the administrators guide. I believe that this is true server side but it is not true client side. On the client side the default is (at least in 3.3.2) this:

packetLen = Integer.getInteger("jute.maxbuffer", 4096 * 1024);

On the server side the documentation looks to be correct:
private static int determineMaxBuffer() {
String maxBufferString = System.getProperty("jute.maxbuffer");
try

{ return Integer.parseInt(maxBufferString); }

catch(Exception e)

{ return 0xfffff; }

}

The documentation states this:
jute.maxbuffer:
(Java system property: jute.maxbuffer)

This option can only be set as a Java system property. There is no zookeeper prefix on it. It specifies the maximum size of the data that can be stored in a znode. The default is 0xfffff, or just under 1M. If this option is changed, the system property must be set on all servers and clients otherwise problems will arise. This is really a sanity check. ZooKeeper is designed to store data on the order of kilobytes in size.

Issue Links

• Is contained by: ZOOKEEPER-2402 Document client side properties
• relates to: ZOOKEEPER-3593 fix the default value of jute.maxbuffer in client side and an optimization for the documentation