You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Paul Otto (JIRA)" <ji...@apache.org> on 2014/08/20 21:14:27 UTC
[jira] [Created] (KAFKA-1606) Reference to old zk.connect vs
broker.list found in docs under Produce APIs
Paul Otto created KAFKA-1606:
--------------------------------
Summary: 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
Priority: Trivial
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.2#6252)