Guozhang,
can you point me to the code that implements periodic/sticky random
partitioner? I actually like to try it out in our env, even though I assume
it is NOT ported to 0.8.2 java producer.
Thanks,
Steven
On Mon, Dec 8, 2014 at 1:43 PM, Guozhang Wang wangg...@gmail.com wrote:
Hi Yury,
Steven,
You can take a look at kafka.producer.async.DefaultEventHandler, in
getPartition function.
Guozhang
On Thu, Dec 11, 2014 at 9:58 AM, Steven Wu stevenz...@gmail.com wrote:
Guozhang,
can you point me to the code that implements periodic/sticky random
partitioner? I actually like to
Hi Yury,
Originally the producer behavior under null-key is random random, but
later changed to this periodic random to reduce the number of sockets on
the server side: imagine if you have n brokers and m producers where m
n, with random random distribution each server will need to maintain a
Hello,
I've come across a (seemingly) strange situation when my Kafka producer
gave so uneven distribution across partitions. I found that I used null key
to produce messages, guided by the following clause in the documentation:
If the key is null, then a random broker partition is picked.
Yes, it is *very* misleading in my opinion - I've seen so many people
surprised with that behaviour...
Technically it's 100% correct of course: If the key is null, then the
Producer will assign the message to a random Partition. - that's what
actually happens, because assignment is random.
If you look under Producer configs you see the following key
‘topic.metadata.refresh.interval.ms’ with a default of 600 * 1000 (10 minutes).
It is not entirely clear but this controls how often a producer will a null key
partitioner will switch partitions that it is writing to. In my production
