[
https://issues.apache.org/jira/browse/KAFKA-2176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14539429#comment-14539429
]
Igor Maravić commented on KAFKA-2176:
-------------------------------------
Didn't know that.
How much is this battle tested? We had a lot of issues with new producer, and
by looking at the mailing lists a lot of other people are having problems with
it.
In our case, we just reverted to use the old Kafka Producer for our internal
API.
But my point is that I still think that the patch is relevant, since the old
producer is still used.
> DefaultPartitioner doesn't perform consistent hashing based on
> ---------------------------------------------------------------
>
> Key: KAFKA-2176
> URL: https://issues.apache.org/jira/browse/KAFKA-2176
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.1
> Reporter: Igor Maravić
> Labels: easyfix, newbie
> Fix For: 0.8.1
>
> Attachments: KAFKA-2176.patch
>
>
> While deploying MirrorMakers in production, we configured it to use
> kafka.producer.DefaultPartitioner. By doing this and since we had the same
> amount partitions for the topic in local and aggregation cluster, we expect
> that the messages will be partitioned the same way.
> This wasn't the case. Messages were properly partitioned with
> DefaultPartitioner on our local cluster, since the key was of the type String.
> On the MirrorMaker side, the messages were not properly partitioned.
> Problem is that the Array[Byte] doesn't implement hashCode function, since it
> is mutable collection.
> Fix is to calculate the deep hash code if the key is of Array type.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
