[
https://issues.apache.org/jira/browse/ZOOKEEPER-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth resolved ZOOKEEPER-4908.
--------------------------------------
Resolution: Invalid
Hello [~alphachb520]. For more discussion of {{jute.maxbuffer}}, refer to the
documentation here:
https://zookeeper.apache.org/doc/r3.9.3/zookeeperAdmin.html
The general guidance is that ZooKeeper is designed to store relatively small
pieces of information in each znode. Storing large data may introduce latency
spikes or quorum instability. Because of that, the community guidance is to
stick with the default of 1 MB. You are free to adjust it higher, but be aware
of the trade-offs, and consider if there are ways to make design changes to
shrink the amount of data you need to store in a znode.
If you need follow-up discussion, I recommend moving to the
[email protected] mailing list.
> Zookeeper encountered an abnormal startup issue with jute.maxbuffer
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-4908
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4908
> Project: ZooKeeper
> Issue Type: Improvement
> Components: jute
> Affects Versions: 3.6.2
> Reporter: cheng
> Assignee: Chris Nauroth
> Priority: Critical
>
> ZooKeeper encountered a jute.maxbuffer restriction issue while loading the
> database. The default size of the current jute.maxbuffer is 1MB (1048575
> bytes), but the length displayed in the log is 2429535, which far exceeds
> this value, resulting in an Unreasonable leLength error. Does the official
> stance not recommend modifying the jute.maxbuffer parameter, or can the
> configuration of jute.maxbuffer be moderately increased? If adjustable, what
> is the recommended value
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
