[jira] [Updated] (KAFKA-4083) ReassignPartitionsCommand does not check replication factor

["Ewen Cheslack-Postava (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-4083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ewen Cheslack-Postava updated KAFKA-4083:
-----------------------------------------
    Fix Version/s:     (was: 0.10.0.0)
                       (was: 0.9.0.0)
                       (was: 0.8.2.0)

Removing fix versions which don't apply since all the labeled fix versions have already been released... As this is a minor bug it probably doesn't need a fix version assigned until the patch lands.

> ReassignPartitionsCommand does not check replication factor
> -----------------------------------------------------------
>
>                 Key: KAFKA-4083
>                 URL: https://issues.apache.org/jira/browse/KAFKA-4083
>             Project: Kafka
>          Issue Type: Bug
>          Components: admin, core
>    Affects Versions: 0.8.2.0, 0.9.0.0, 0.10.0.0
>         Environment: Linux 14.04 LTS, Scala 2.10
>            Reporter: Simon Wan Wenli
>            Assignee: Simon Wan Wenli
>            Priority: Minor
>              Labels: newbie
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> ReassignPartitionsCommand does not check whether the replication factor of a partition is the same as existing replication factor, which may result that different partitions of a topic have different number of replicas. More specifically, TopicCommand will throw exception which contains "All partitions should have the same number of replicas." as the message when the user tries to add partitions. I think this loophole also may leave Kafka in a situation from which it is difficult to recover.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)