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

Posted to jira@kafka.apache.org by "dengziming (Jira)" <ji...@apache.org> on 2022/09/13 07:08:00 UTC

[jira] [Commented] (KAFKA-14152) Add logic to fence kraft brokers which have fallen behind in replication

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

dengziming commented on KAFKA-14152:
------------------------------------

> it must catch up to the current metadata before it is unfenced.

Currently, we have changed the behavior to unfence a broker when it catch up to it's own RegisterBrokerRecord.

> Add logic to fence kraft brokers which have fallen behind in replication
> ------------------------------------------------------------------------
>
>                 Key: KAFKA-14152
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14152
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Jason Gustafson
>            Priority: Major
>
> When a kraft broker registers with the controller, it must catch up to the current metadata before it is unfenced. However, once it has been unfenced, it only needs to continue sending heartbeats to remain unfenced. It can fall arbitrarily behind in the replication of the metadata log and remain unfenced. We should consider whether there is an inverse condition that we can use to fence a broker that has fallen behind.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)