Swapnil
What do you mean by "I did a local test today that showed that choosing
DefaultPartitioner with
null key in the messages appended data to multiple partitions"?
Are messages being duplicated across partitions?
-Chetan
On Sat, Sep 14, 2013 at 9:02 PM, Swapnil Ghike wrote:
> Hi Joe, Dre
Hi Joe, Drew,
In 0.8 HEAD, if the key is null, the DefaultEventHandler randomly chooses
an available partition and never calls the partitioner.partition(key,
numPartitions) method. This is done in lines 204 to 212 of the github
commit Drew pointed to, though that piece of code is slightly differen
Prashant
I recall you mentioning that you are on the 0.8 branch ..
If so, can you check your producer to verify if you are using
DefaultParitioner, SimplePartitioner or null (which defaults to
RandomParitioner)?
*kafkaProps.put("partitioner.class", "kafka.producer.DefaultPartitioner") *
Also ,
Hi Prashant,
I tried a local test using a very short topic.metadata.refresh.interval.ms
on the producer. The server had two partitions and both of them appended
data. Could you check if you have set the
topic.metadata.refresh.interval.ms on your producer to a very high value?
Swapnil
On 9/13/13
