t messages which were polled before but stayed
unprocessed because of the
// error
consumer.commit(map,
CommitType.SYNC);
}
}
Does this approach make sense?
--
Stefan Miklosovic
> Have you looked at the following output for message distribution
>> across the topic-partitions and which topic-partition is consumed by
>> which consumer thread?
>>
>> kafaka-server/bin>./kafka-run-class.sh
>> kafka.tools.ConsumerOffsetChecker --zkconnect localhos
distribution
>> across the topic-partitions and which topic-partition is consumed by
>> which consumer thread?
>>
>> kafaka-server/bin>./kafka-run-class.sh
>> kafka.tools.ConsumerOffsetChecker --zkconnect localhost:2181 --group
>>
>>
>> Jagbir
>
consumer thread?
>
> kafaka-server/bin>./kafka-run-class.sh
> kafka.tools.ConsumerOffsetChecker --zkconnect localhost:2181 --group
>
>
> Jagbir
>
> On Wed, Jul 15, 2015 at 12:50 PM, Stefan Miklosovic
> wrote:
>> I have following problem, I tried almost everything
ible so
to be super sure about the even spreading of message to partitions, I
used custom partitioner class in old consumer so I will be sure that
the partition the message will be sent to is super random.
But that does not seems to work either.
Please people, help me.
--
Stefan Miklosovic
the
first place.
Why partitions are not spread evenly accross all consumers?
(1) https://issues.apache.org/jira/browse/KAFKA-2331
--
Stefan Miklosovic