[
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14964009#comment-14964009
]
Flavio Junqueira commented on KAFKA-2017:
-----------------------------------------
[~guozhang]
bq. With this data size a 5 node ZK should be able to handle at least 10K / sec
writes with latency around couple of ms on HDD, and on SSD latency should be
much less
The figures are right. With SSDs, you should be able to get sub-millisecond
latency.
bq. unless we have scenarios that each consumer forms a single group then it
should be fine: in this case it would be the same as offset commits in ZK
anyways.
I didn't quite get the comment about each consumer forming a single group. How
does impact the zookeeper traffic?
> 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)
