[
https://issues.apache.org/jira/browse/KAFKA-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao resolved KAFKA-1606.
----------------------------
Resolution: Fixed
Assignee: Jun Rao
Thanks for pointing this out. Fixed the website.
> Reference to old zk.connect vs broker.list found in docs under Produce APIs
> ---------------------------------------------------------------------------
>
> Key: KAFKA-1606
> URL: https://issues.apache.org/jira/browse/KAFKA-1606
> Project: Kafka
> Issue Type: Bug
> Components: website
> Affects Versions: 0.8.1
> Environment: any
> Reporter: Paul Otto
> Assignee: Jun Rao
> Priority: Trivial
> Labels: documentation, producer
>
> Current documentation for Kafka 0.8.1 has the following under 5.1 API Design
> / Producer APIs:
> * provides ZooKeeper based automatic broker discovery -
> The ZooKeeper based broker discovery and load balancing can be used by
> specifying the ZooKeeper connection url through the zk.connect config
> parameter. For some applications, however, the dependence on ZooKeeper is
> inappropriate. In that case, the producer can take in a static list of
> brokers through the broker.list config parameter. Each produce requests gets
> routed to a random broker partition in this case. If that broker is down, the
> produce request fails.
> This does not seem correct anymore as 1) zk.connect is no longer a valid
> parameter; and 2) the way the broker list is handled has changed from the
> above description.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
