You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: zookeeper-docs/src/main/resources/markdown/zookeeperAdmin.md
+16-8Lines changed: 16 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1384,15 +1384,23 @@ the variable does.
1384
1384
set to no, ZooKeeper will not require updates to be synced to
1385
1385
the media.
1386
1386
1387
-
**jute.maxbuffer:* :
1388
-
(Java system property:**jute.maxbuffer**)
1389
-
This option can only be set as a Java system property.
1387
+
**jute.maxbuffer* :
1388
+
(Java system property:**jute.maxbuffer**).
1389
+
-This option can only be set as a Java system property.
1390
1390
There is no zookeeper prefix on it. It specifies the maximum
1391
-
size of the data that can be stored in a znode. The default is
1392
-
0xfffff, or just under 1M. If this option is changed, the system
1393
-
property must be set on all servers and clients otherwise
1394
-
problems will arise. This is really a sanity check. ZooKeeper is
1395
-
designed to store data on the order of kilobytes in size.
1391
+
size of the data that can be stored in a znode. The unit is: byte. The default is
1392
+
0xfffff(1048575) bytes, or just under 1M.
1393
+
- If this option is changed, the system property must be set on all servers and clients otherwise
1394
+
problems will arise.
1395
+
- When *jute.maxbuffer* in the client side is greater than the server side, the client wants to write the data
1396
+
exceeds *jute.maxbuffer* in the server side, the server side will get **java.io.IOException: Len error**
1397
+
- When *jute.maxbuffer* in the client side is less than the server side, the client wants to read the data
1398
+
exceeds *jute.maxbuffer* in the client side, the client side will get **java.io.IOException: Unreasonable length**
1399
+
or **Packet len is out of range!**
1400
+
- This is really a sanity check. ZooKeeper is designed to store data on the order of kilobytes in size.
1401
+
In the production environment, increasing this property to exceed the default value is not recommended for the following reasons:
1402
+
- Large size znodes cause unwarranted latency spikes, worsen the throughput
1403
+
- Large size znodes make the synchronization time between leader and followers unpredictable and non-convergent(sometimes timeout), cause the quorum unstable
1396
1404
1397
1405
**jute.maxbuffer.extrasize*:
1398
1406
(Java system property: **zookeeper.jute.maxbuffer.extrasize**)
Copy file name to clipboardExpand all lines: zookeeper-docs/src/main/resources/markdown/zookeeperProgrammers.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1305,10 +1305,11 @@ following reference
1305
1305
and the password to unlock the file.
1306
1306
1307
1307
* *jute.maxbuffer* :
1308
-
It specifies the maximum size of the incoming data from the server. The default value is 4194304
1309
-
Bytes , or just 4 MB. This is really a sanity check. The ZooKeeper server is designed to store and send
1308
+
In the client side, it specifies the maximum size of the incoming data from the server. The default is 0xfffff(1048575) bytes,
1309
+
or just under 1M. This is really a sanity check. The ZooKeeper server is designed to store and send
1310
1310
data on the order of kilobytes. If incoming data length is more than this value, an IOException
1311
-
is raised.
1311
+
is raised. This value of client side should keep same with the server side(Setting **System.setProperty("jute.maxbuffer", "xxxx")** in the client side will work),
1312
+
otherwise problems will arise.
1312
1313
1313
1314
* *zookeeper.kinit* :
1314
1315
Specifies path to kinit binary. Default is "/usr/bin/kinit".
0 commit comments