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

Posted to jira@kafka.apache.org by "Agam Brahma (Jira)" <ji...@apache.org> on 2020/02/25 21:00:00 UTC

[jira] [Assigned] (KAFKA-9347) Detect deleted log directory before becoming leader

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

Agam Brahma reassigned KAFKA-9347:
----------------------------------

    Assignee: Agam Brahma

> Detect deleted log directory before becoming leader
> ---------------------------------------------------
>
>                 Key: KAFKA-9347
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9347
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Assignee: Agam Brahma
>            Priority: Major
>              Labels: needs-discussion
>
> There is no protection currently if a broker has had its log directory deleted to prevent it from becoming the leader of a partition that it still remains in the ISR of. This scenario can happen when the last remaining replica in the ISR is shutdown. It will remain in the ISR and be eligible for leadership as soon as it starts up. It would be useful to either detect this case situation dynamically in order to force the user to do an unclean election or recover another broker. One option might be just to pass a flag on startup to specify that a broker should not be eligible for leadership. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)