The producer in 0.8 doesn't depend on a VIP to connect to the brokers.
Instead, it obtains metadata from a list of brokers (or a VIP in front of
the brokers) and finds out the host/port of the broker for the leader
replica of each partition in a topic. It then establishes socket
connections to those brokers directly. If a message doesn't provide a key,
the producer will pick a random and available partition to send the data.
On send failures, metadata will be refreshed to pick up the new leaders of
the partitions. Metadata is also refreshed periodically to pick up any
newly added partitions.


On Fri, Sep 27, 2013 at 8:12 AM, Nicolae Marasoiu <[EMAIL PROTECTED]>wrote:
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB