You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "Chris Nauroth (Jira)" <ji...@apache.org> on 2025/03/18 21:51:00 UTC

[jira] [Assigned] (ZOOKEEPER-4908) Zookeeper encountered an abnormal startup issue with jute.maxbuffer

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-4908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Nauroth reassigned ZOOKEEPER-4908:
----------------------------------------

    Assignee: Chris Nauroth

> 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)