[
https://issues.apache.org/jira/browse/KAFKA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093110#comment-14093110
]
Guozhang Wang commented on KAFKA-1586:
--------------------------------------
I think while we are designing the new producer, we have decided to use a fixed
partitioner, and let application logic to specify the partition id if they want
some sort of stickiness. I am wondering if we shall just implement this sticky
logic in the application level, such as MirrorMaker instead of make it inside
the new producer?
> 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)
