Re: PartitionAssignor / Sort members per subscription time before assigning partitions

2016-09-05 Thread Florian Hussonnois
Hi Jason, The downside to use client-ids is there is no certitude that they will be increasing. So in case there is already as many consumers as partitions, additional consumers can change the partitions assignment. This lead to rebalances which are unnecessary as partitions are already

Re: PartitionAssignor / Sort members per subscription time before assigning partitions

2016-09-01 Thread Jason Gustafson
Hi Florian, I'm not totally sure I understand the problem. The consumer id consists of the clientId configured by the user with a UUID appended to it. If the clientId has not been passed in configuration, we use "consumer-{n}" for it where n is incremented for every new consumer instance. Is the

PartitionAssignor / Sort members per subscription time before assigning partitions

2016-09-01 Thread Florian Hussonnois
Hi Kafka Team, I would like to have your opinion before creating a new JIRA. I'm working with the Java Consumer API. The current partition assignors use the consumer ids to sort members before assigning partitions. This works pretty well as long as all consumers are started into the same JVM