[
https://issues.apache.org/jira/browse/KAFKA-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ismael Juma resolved KAFKA-13270.
---------------------------------
Assignee: Ismael Juma (was: Ron Dagostino)
Resolution: Fixed
> Kafka may fail to connect to ZooKeeper, retry forever, and never start
> ----------------------------------------------------------------------
>
> Key: KAFKA-13270
> URL: https://issues.apache.org/jira/browse/KAFKA-13270
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.0.0
> Reporter: Ron Dagostino
> Assignee: Ismael Juma
> Priority: Blocker
> Fix For: 3.0.0
>
>
> The implementation of https://issues.apache.org/jira/browse/ZOOKEEPER-3593 in
> ZooKeeper version 3.6.0 decreased the default value for the ZooKeeper
> client's `jute.maxbuffer` configuration from 4MB to 1MB. This can cause a
> problem if Kafka tries to retrieve a large amount of data across many znodes
> -- in such a case the ZooKeeper client will repeatedly emit a message of the
> form "java.io.IOException: Packet len <####> is out of range" and the Kafka
> broker will never connect to ZooKeeper and fail to make progress on the
> startup sequence. We can avoid the potential for this issue to occur by
> explicitly setting the value to 4MB whenever we create a new ZooKeeper client
> as long as no explicit value has been set via the `jute.maxbuffer` system
> property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
