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

Posted to dev@kafka.apache.org by "Colin McCabe (Jira)" <ji...@apache.org> on 2022/04/20 21:38:00 UTC

[jira] [Created] (KAFKA-13841) Fix a case where we were unable to place on fenced brokers In KRaft mode

Colin McCabe created KAFKA-13841:
------------------------------------

             Summary: Fix a case where we were unable to place on fenced brokers In KRaft mode
                 Key: KAFKA-13841
                 URL: https://issues.apache.org/jira/browse/KAFKA-13841
             Project: Kafka
          Issue Type: Bug
            Reporter: Colin McCabe


This PR fixes a case where we were unable to place on fenced brokers In KRaft mode. Specifically, if we had a broker registration in the metadata log, but no associated heartbeat, previously the HeartbeatManager would not track the fenced broker. This PR fixes this by adding this logic to the metadata log replay path in ClusterControlManager.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)