Home | About | Sematext search-lucene.com search-hadoop.com search-devops.com metrics + logs = try SPM and Logsene for free
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
 Search Hadoop and all its subprojects:

Switch to Threaded View
Kafka >> mail # user >> How does Kafka decide which Consumer out of multiple Consumer clients to assign to a single topic partition


Copy link to this message
-
Re: How does Kafka decide which Consumer out of multiple Consumer clients to assign to a single topic partition
Hello Dennis,

The rebalance on each consumer works by first release their owned
partitions first (releasePartitionOwnership in
ZookeeperConsumerConnector.scala) and then compute the new ownership. Hence
in your scenario it is equally possible for each one of the two consumers
to own the partition in each rebalance process. And it is  not possible to
predict which consumer will claim the ownership of the partition.

Guozhang
On Thu, Aug 22, 2013 at 8:53 AM, Dennis Haller <[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