[
https://issues.apache.org/jira/browse/KAFKA-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michał Michalski updated KAFKA-1531:
------------------------------------
Description: I've noticed that Kafka tarball comes with
zookeeper.connection.timeout.ms=1000000 in server.properties while
https://kafka.apache.org/08/documentation.html says the default is 6000. This
setting was introduced in configuration file in 46b6144a, so quite a long time
ago (3 years), which makes it look intentional, but as per Jun Rao's comment on
IRC, 6000 sounds more reasonable, so that entry should probably be changed or
removed from config at all. (was: I've noticed that Kafka tarball comes with
zookeeper.connection.timeout.ms=1000000 in server.properties while
https://kafka.apache.org/08/documentation.html says the default is 6000. This
setting was introduced in configuration file in 46b6144a, so quite a long time
ago (3 years), so it looks intentional, but as per Jun Rao's comment on IRC,
6000 sounds more reasonable, so that entry should probably be changed or
removed from config at all.)
> zookeeper.connection.timeout.ms is set to 10000000 in configuration file in
> Kafka tarball
> -----------------------------------------------------------------------------------------
>
> Key: KAFKA-1531
> URL: https://issues.apache.org/jira/browse/KAFKA-1531
> Project: Kafka
> Issue Type: Bug
> Components: config
> Affects Versions: 0.8.0, 0.8.1.1
> Reporter: Michał Michalski
>
> I've noticed that Kafka tarball comes with
> zookeeper.connection.timeout.ms=1000000 in server.properties while
> https://kafka.apache.org/08/documentation.html says the default is 6000. This
> setting was introduced in configuration file in 46b6144a, so quite a long
> time ago (3 years), which makes it look intentional, but as per Jun Rao's
> comment on IRC, 6000 sounds more reasonable, so that entry should probably be
> changed or removed from config at all.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
