[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959392#comment-14959392
]
Joel Koshy commented on KAFKA-2017:
-----------------------------------
btw, I just realized a migration as described above probably won't work - since
we would need all consumers to participate in a rebalance to migrate state from
zookeeper to Kafka (if we ever want to do that). We could think of other
migration strategies but if there is no easy migration strategy then I think it
is more important to make a sound choice now that most people are comfortable
with. To summarize:
* I think persistence in ZK is okay and should work
* Persistence in Kafka seems better, but implementation in Kafka is a little
more work.
* We definitely need persistence in 0.9.
* If we do persistence in ZK and discover use-cases where it doesn't scale then
migration may be difficult.
Okay so those are the observations. Anything else? Basically IMO it boils down
to an okay solution vs a good solution. i.e., I personally think it is okay to
do it in ZK and I'm not uncomfortable with it. If we are cool with spending
some more time to implement in Kafka I would prefer that approach.
> Persist Coordinator State for Coordinator Failover
> --------------------------------------------------
>
> Key: KAFKA-2017
> URL: https://issues.apache.org/jira/browse/KAFKA-2017
> Project: Kafka
> Issue Type: Sub-task
> Components: consumer
> Affects Versions: 0.9.0.0
> Reporter: Onur Karaman
> Assignee: Guozhang Wang
> Fix For: 0.9.0.0
>
> Attachments: KAFKA-2017.patch, KAFKA-2017_2015-05-20_09:13:39.patch,
> KAFKA-2017_2015-05-21_19:02:47.patch
>
>
> When a coordinator fails, the group membership protocol tries to failover to
> a new coordinator without forcing all the consumers rejoin their groups. This
> is possible if the coordinator persists its state so that the state can be
> transferred during coordinator failover. This state consists of most of the
> information in GroupRegistry and ConsumerRegistry.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
