[
https://issues.apache.org/jira/browse/KAFKA-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13201697#comment-13201697
]
Neha Narkhede commented on KAFKA-264:
-------------------------------------
If a process goes down, the ephemeral node for /consumers/[group]/leader will
get deleted from Zookeeper. Each consumer process listens on that path, and
triggers a leader election. However, these are very low level details of the
implementation, which I intended to chalk out after the high level design
looked good.
You can read more about Zookeeper based leader election here -
http://zookeeper.apache.org/doc/trunk/recipes.html#sc_leaderElection
> Change the consumer side load balancing and distributed co-ordination to use
> a consumer co-ordinator
> ----------------------------------------------------------------------------------------------------
>
> Key: KAFKA-264
> URL: https://issues.apache.org/jira/browse/KAFKA-264
> Project: Kafka
> Issue Type: New Feature
> Components: core
> Affects Versions: 0.7
> Reporter: Neha Narkhede
> Assignee: Neha Narkhede
> Fix For: 0.7.1
>
> Original Estimate: 672h
> Remaining Estimate: 672h
>
> A high level design for the zookeeper consumer is here -
> https://cwiki.apache.org/confluence/display/KAFKA/Consumer+co-ordinator
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
