kafka-jira mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KAFKA-6650) The controller should be able to handle a partially deleted topic
Date Wed, 04 Apr 2018 21:01:00 GMT

    [ https://issues.apache.org/jira/browse/KAFKA-6650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426161#comment-16426161

ASF GitHub Bot commented on KAFKA-6650:

gitlw opened a new pull request #4825: KAFKA-6650: Allowing transition to OfflineReplica state
for replicas without leadership info
URL: https://github.com/apache/kafka/pull/4825
   A partially deleted topic can end up with some partitions having no leadership info.
   For the partially deleted topic, a new controller should be able to finish the topic deletion
   by transitioning the rogue partition's replicas to OfflineReplica state.
   This patch adds logic to transition replicas to OfflineReplica state whose partitions have
   no leadership info.
   Added a new test method to cover the partially deleted topic case.
   ### Committer Checklist (excluded from commit message)
   - [ ] Verify design and implementation 
   - [ ] Verify test coverage and CI build status
   - [ ] Verify documentation (including upgrade notes)

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

> 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
> 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

View raw message