You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Jun Rao (JIRA)" <ji...@apache.org> on 2018/04/17 00:18:00 UTC

[jira] [Resolved] (KAFKA-6650) The controller should be able to handle a partially deleted topic

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

Jun Rao resolved KAFKA-6650.
----------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

merged the PR to trunk.

> The controller should be able to handle a partially deleted topic
> -----------------------------------------------------------------
>
>                 Key: KAFKA-6650
>                 URL: https://issues.apache.org/jira/browse/KAFKA-6650
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Lucas Wang
>            Assignee: Lucas Wang
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> A previous controller could have deleted some partitions of a topic from ZK, but not all partitions, and then died.
> In that case, the new controller should be able to handle the partially deleted topic, and finish the deletion.
> In the current code base, if there is no leadership info for a replica's partition, the transition to OfflineReplica state for the replica will fail. Afterwards the transition to ReplicaDeletionStarted will fail as well since the only valid previous state for ReplicaDeletionStarted is OfflineReplica. Furthermore, it means the topic deletion will never finish.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)