[
https://issues.apache.org/jira/browse/KAFKA-7382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621066#comment-16621066
]
Suman B N commented on KAFKA-7382:
----------------------------------
Working on this. I already have a fix for this.
> We shoud guarantee at lest one replica of partition should be alive when
> create or update topic
> -----------------------------------------------------------------------------------------------
>
> Key: KAFKA-7382
> URL: https://issues.apache.org/jira/browse/KAFKA-7382
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.2.0
> Reporter: zhaoshijie
> Priority: Major
>
> For example：I have brokers: 1,2,3,4,5. I create a new topic by command:
> {code:java}
> sh kafka-topics.sh --create --topic replicaserror --zookeeper localhost:2181
> --replica-assignment 11:12:13,12:13:14,14:15:11,14:12:11,13:14:11
> {code}
> Then kafkaController will process this,after partitionStateMachine and
> replicaStateMachine handle state change,topic metadatas and state will be
> strange,partitions is on NewPartition and replicas is on OnlineReplica.
> Next wo can not delete this topic（bacase state change illegal ）,This will
> cause a number of problems.So i think wo shoud check replicas assignment when
> create or update topic.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
