[
https://issues.apache.org/jira/browse/KAFKA-7362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804577#comment-16804577
]
xiongqi wu commented on KAFKA-7362:
-----------------------------------
Yes, I am stilling looking forward on fixing this issue.
I was on hold on this item because
1) there is no active discussion on KIP-370.
2) I am also thinking about combing this with topic deletion. Today a topic
can only be deleted when all related brokers are online. This causes topic
deletion to stuck if a broker fails and never come back again. I was thinking
combining this feature with the change of topic deletion state machine so that
topic deletion can always success and orphan partitions can be safely removed
when offline brokers come back online.
I will update the ticket and KIP-370 after I think a little more about item 2.
> enable kafka broker to remove orphan partitions automatically
> --------------------------------------------------------------
>
> Key: KAFKA-7362
> URL: https://issues.apache.org/jira/browse/KAFKA-7362
> Project: Kafka
> Issue Type: Improvement
> Components: core, log
> Reporter: xiongqi wu
> Assignee: xiongqi wu
> Priority: Major
>
> When partition reassignment removes topic partitions from a offline broker,
> those removed partitions become orphan partitions to the broker. When the
> offline broker comes back online, it is not able to clean up both data and
> folders that belong to orphan partitions. Log manager will scan all all dirs
> during startup, but the time based retention policy on a topic partition will
> not be kicked out until the broker is either a follower or a leader of the
> partition. In addition, we do not have logic to delete folders that belong
> to orphan partition today.
> Open this ticket to provide a mechanism (when enabled) to safely remove
> orphan partitions automatically.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
