[
https://issues.apache.org/jira/browse/KAFKA-3818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15326100#comment-15326100
]
Ewen Cheslack-Postava commented on KAFKA-3818:
----------------------------------------------
Like all changes to defaults, doesn't this require a round of warnings about
impending changes and ideally the change made on a major release cycle with
appropriate docs changes? Should we make the first patch just the addition of a
warning of change + docs changes and then schedule subsequent patch for later
release?
> 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)
