[
https://issues.apache.org/jira/browse/KAFKA-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14093140#comment-14093140
]
Jun Rao commented on KAFKA-1586:
--------------------------------
The question is whether sticky partitioning only helps MirrorMaker or all
producers. If it's the former, it may make sense to do it just in MirrorMaker.
Otherwise, doing this in the producer itself is more convenient. To me, this
feature can be useful for any producer that cares about compression ratio
and/or # of concurrent socket connections.
> 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)
