[
https://issues.apache.org/jira/browse/KAFKA-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15325441#comment-15325441
]
ASF GitHub Bot commented on KAFKA-3818:
---------------------------------------
GitHub user vahidhashemian opened a pull request:
https://github.com/apache/kafka/pull/1493
KAFKA-3818: Change Mirror Maker default assignment strategy to round robin
Update Mirror Maker to use round robin assignment by default since it gives
a better balance between the instances, in particular when the number of Mirror
Maker instances exceeds the typical number of partitions per topic. There
doesn't seem to be any need to keep range assignment since co-partitioning is
not an issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/vahidhashemian/kafka KAFKA-3818
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1493.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1493
----
commit 24884d4ab13294d9e557e0698e9dafb672155208
Author: Vahid Hashemian <vahidhashem...@us.ibm.com>
Date: 2016-06-10T22:29:06Z
KAFKA-3818: Change Mirror Maker default assignment strategy to round robin
It might make more sense to use round robin assignment by default for
Mirror Maker since it gives a better balance between the instances,
in particular when the number of Mirror Maker instances exceeds the typical
number of partitions per topic.
There doesn't seem to be any need to keep range assignment since
copartitioning is not an issue.
----
> Change Mirror Maker default assignment strategy to round robin
> --------------------------------------------------------------
>
> Key: KAFKA-3818
> URL: https://issues.apache.org/jira/browse/KAFKA-3818
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Vahid Hashemian
>
> It might make more sense to use round robin assignment by default for MM
> since it gives a better balance between the instances, in particular when the
> number of MM instances exceeds the typical number of partitions per topic.
> There doesn't seem to be any need to keep range assignment since
> copartitioning is not an issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
