[
https://issues.apache.org/jira/browse/KAFKA-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14063541#comment-14063541
]
Manikumar Reddy edited comment on KAFKA-1531 at 7/16/14 2:35 PM:
-----------------------------------------------------------------
Previous patch I tried to update all the conf files across all the folders
config, various test_suite etc..
Latest patch contains changes related to config/server.properties and
config/consumer.properties only.
I think latest changes are sufficient for preparing kafka tar release.
was (Author: omkreddy):
Previous patch I tried to update all the conf files across all the folders
config, various test_suite etc..
Latest patch contains changes related to server.properties and
consumer.properties only.
I think latest changes are sufficient for preparing kafka tar release.
> 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
> Assignee: Manikumar Reddy
> Attachments: KAFKA-1531.patch, KAFKA-1531.patch
>
>
> 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)
