Thanks Guozhang!
Cheers,
Churu
On Mar 17, 2014, at 3:48 PM, Guozhang Wang wrote:
> The short answer to both questions is yes.
>
> For the second question, the long answer will be: on startup of the
> high-level consumer, it will register itself under its ZK group path, so it
> knows other memb
The short answer to both questions is yes.
For the second question, the long answer will be: on startup of the
high-level consumer, it will register itself under its ZK group path, so it
knows other members in the group also; and upon rebalance triggered, it
will read its peer number, and also the
Hi Guozhang,
I really appreciate the detailed explanation!
Does this mean that the rule “1 partition will be consumed by exactly one
consumer in the consumer group” will only be checked and ensured at the
consumer side? Also, does the “consumer group registration in Zookeeper” need
to be taken
Hi Churu,
Brokers are actually not aware of the consumer groups, the consumer groups
is maintained within the consumers (and registered in ZK) to achieve load
balance. After the group has decided who-consume-which-partition, then each
consumer will do their fetching independently and send fetching
Hi,
“Consumers label themselves with a consumer group name”, and consumer group
name should be global across each Kafka cluster. However, when I check the API,
there is no “consumer group name” included in any kind of request(metadata,
produce, fetch, offset). Does the broker know about the con
