[
https://issues.apache.org/jira/browse/KAFKA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093185#comment-14093185
]
Jay Kreps commented on KAFKA-1586:
----------------------------------
We made partitioning pluggable so you could plug in the partitioning strategy
of your choice. I think this is the right route rather than trying to implement
every possible partitioning strategy in the producer. In my experience ~100% of
people who have experienced the sticky partitioning feature think it is a bug
and don't understand how to turn it off. ~0% of people want this feature
outside LinkedIn which is trying to reduce the connection count. So I think it
makes sense to have LinkedIn just implement their own partitioning strategy.
> support sticky partitioning in the new producer
> -----------------------------------------------
>
> Key: KAFKA-1586
> URL: https://issues.apache.org/jira/browse/KAFKA-1586
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.2
> Reporter: Jun Rao
> Assignee: Jun Rao
> Attachments: KAFKA-1586.patch
>
>
> If a message doesn't specify a key or a partition, the new producer selects a
> partition for each message in a round-robin way. As a result, in a window of
> linger.ms, messages are spread around in all partitions of a topic. Compared
> with another strategy that assigns all messages to a single partition in the
> same time window, this strategy may not compress the message set as well
> since the batch is smaller. Another potential problem with this strategy is
> that the compression ratio could be sensitive to the change of # partitions
> in a topic. If # partitions are increased in a topic, the produced data may
> not be compressed as well as before.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
