Search Hadoop and all its sub project:

Switch to Threaded View
Subject: Re: Kafka wiki Documentation conventions - looking for feedback
Basically, every time a consumer joins a group, every consumer in the
groups gets a ZK notification and each of them tries to own a subset of the
total number of partitions. A given partition is only assigned to one of
the consumers in the same group. Once the ownership is determined, each
consumer consumes messages coming from its partitions and manages the
offset of those partitions. Since at any given point of time, a partition
is only owned by one consumer, there won't be conflicts on updating the
offsets. More details are described in the "consumer rebalancing algorithm"
section of


On Mon, Apr 29, 2013 at 8:16 AM, Chris Curtin <[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