Hi Vahid, Thanks for the proposal. I think one of the advantages of having sticky assignment would be reduce the need to cleanup local partition state between rebalances. Do you have any thoughts on how the user would take advantage of this assignor in the consumer to do this? Maybe one approach is to delay cleanup until you detect a change from the previous assignment in the onPartitionsAssigned() callback?
Also, can you provide some detail on how the sticky assignor works at the group protocol level? For example, do you pass old assignments through the "UserData" field in the consumer's JoinGroup? Thanks, Jason On Thu, Apr 14, 2016 at 11:05 AM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Hi all, > > I have started a new KIP under > > https://cwiki.apache.org/confluence/display/KAFKA/KIP-54+-+Sticky+Partition+Assignment+Strategy > The corresponding JIRA is at > https://issues.apache.org/jira/browse/KAFKA-2273 > The corresponding PR is at https://github.com/apache/kafka/pull/1020 > > Your feedback is much appreciated. > > Regards, > Vahid Hashemian > >
