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

Posted to dev@kafka.apache.org by "bijaya (JIRA)" <ji...@apache.org> on 2019/05/28 20:34:00 UTC

[jira] [Created] (KAFKA-8444) If broker sense that it is unhealthy, broker should remove itself as leader from all partitions that it is hosting as partition leader.

bijaya created KAFKA-8444:
-----------------------------

             Summary: If broker sense that it is unhealthy, broker should remove itself as leader from all partitions that it is hosting as partition leader.
                 Key: KAFKA-8444
                 URL: https://issues.apache.org/jira/browse/KAFKA-8444
             Project: Kafka
          Issue Type: Improvement
          Components: core
    Affects Versions: 2.1.1
            Reporter: bijaya


A broker can have partition leader for more than one partition.

If broker sense any panic with the host like disk write, memory (crashing), network. 

It should send eject me ( like ejecting from fighter jet) from cluster message to cluster controller/zookeeper. Which means its not a part of cluster anymore.

This makes the next leader election quicker and can prevent many issues before it happens.



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