[KAFKA-608] getTopicMetadata does not respect producer config settings

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 0.8.0
• Fix Version/s: 0.8.0
• Assignee: Neha Narkhede
• Reporter: Jay Kreps
• Created: 13/Nov/12 17:58
• Updated: 05/Dec/12 18:32
• Resolved: 03/Dec/12 23:26

Description

ProducerPool.scala contains the following code:
object ProducerPool{
def createSyncProducer(configOpt: Option[ProducerConfig], broker: Broker): SyncProducer =

{ val props = new Properties() props.put("host", broker.host) props.put("port", broker.port.toString) if(configOpt.isDefined) props.putAll(configOpt.get.props.props) new SyncProducer(new SyncProducerConfig(props)) }

}

Note also, that ClientUtils.getTopicMetadata() does the following:
ProducerPool.createSyncProducer(None, brokers)

As a result there is no way to control the socket settings for the get metadata request.

My recommendation is that we require the config to be specified in the

Note that this creates a new sync producer without using ANY of the settings the user had given for the producer. In particular the socket timeout is defaulted to 500ms.

This causes unit tests to fail a lot since a newly started test may easily timeout on a 500ms request.

Issue Links

• contains: KAFKA-630 Auto create topic doesn't reflect the new topic and throws UnknownTopicOrPartitionException