Hey community friends, after another month of polishing, KIP-345<https://cwiki.apache.org/confluence/display/KAFKA/KIP-345%3A+Introduce+static+membership+protocol+to+reduce+consumer+rebalances> design is ready for vote. Feel free to add your comment on the discussion thread or here.
Thanks for your time! Boyang ________________________________ From: Boyang Chen <bche...@outlook.com> Sent: Friday, November 9, 2018 6:35 AM To: dev@kafka.apache.org Subject: [VOTE] KIP-345: Introduce static membership protocol to reduce consumer rebalances Hey all, thanks so much for all the inputs on KIP-345 so far. The original proposal has enhanced a lot with your help. To make sure the implementation go smoothly without back and forth, I would like to start a vote on the final design agreement now: https://cwiki.apache.org/confluence/display/KAFKA/KIP-<https://cwiki.apache.org/confluence/display/KAFKA/KIP-345%3A+Introduce+static+membership+protocol+to+reduce+consumer+rebalances> 345%3A+Introduce+static+membership+protocol+to+reduce+consumer+rebalances<https://cwiki.apache.org/confluence/display/KAFKA/KIP-345%3A+Introduce+static+membership+protocol+to+reduce+consumer+rebalances> KIP-345: Introduce static membership protocol to reduce ...<https://cwiki.apache.org/confluence/display/KAFKA/KIP-345%3A+Introduce+static+membership+protocol+to+reduce+consumer+rebalances> cwiki.apache.org For stateful applications, one of the biggest performance bottleneck is the state shuffling. In Kafka consumer, there is a concept called "rebalance" which means that for given M partitions and N consumers in one consumer group, Kafka will try to balance the load between consumers and ideally have ... Let me know if you have any questions. Best, Boyang
