[
https://issues.apache.org/jira/browse/KAFKA-579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-579.
---------------------------
Resolution: Fixed
Fix Version/s: 0.8
Thanks for the patch. +1. Committed to 0.8 after removing an unused variable
lastConnectionTime in SyncProducer.
> remove connection timeout in SyncProducer
> -----------------------------------------
>
> Key: KAFKA-579
> URL: https://issues.apache.org/jira/browse/KAFKA-579
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8
> Reporter: Jun Rao
> Assignee: Swapnil Ghike
> Priority: Blocker
> Labels: bugs, newbie
> Fix For: 0.8
>
> Attachments: kafka-579-v1.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Currently, SyncProducer has a few parameters that control how long the client
> should wait to establish a socket connection and how frequent the connection
> should be re-established. Those parameters seem to be needed primarily for
> vip on a load balancer. In 0.8, SyncProducer doesn't deal with VIP any more.
> So, we probably should get rid of those parameters. One of the issues that I
> have seen is that when a broker is down, SyncProducer will still wait
> connectionTimeout time to try to establish a connection. This is unnecessary
> since the high level producer already has the retry logic and is delaying
> requests like getMetadataRequest.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
