Peter, Currently the partition assignment could change when there is any change in brokers and consumers in the same group. The change is typically triggered by starting or stopping a broker/consumer. However, it can also happen if the broker/consumer somehow expires its ZK session (e.g., long GC).
Thanks, Jun On Tue, May 1, 2012 at 3:28 PM, Peter Romianowski <honkb...@googlemail.com>wrote: > Hi, > > wer are using the high-level Java consumer. We feed the events received > from Kafka into some sort of state machine. Since we have Kafka's guarantee > that each partition is read by the same consumer, we want to keep the > states in memory to achieve even higher throughput. So it is vital for us > that either a partition is never moved from a running consumer or our code > gets at least informed about that. > > Does Kafka guarantee that a partition assigned to a consumer will stay at > this consumer for the whole lifetime of the jvm? Even in corner cases like > loosing connection to zookeeper? > > Regards, > > Peter >
