Jose Armando Garcia Sancio created KAFKA-13959:
--------------------------------------------------
Summary: Controller should unfence Broker with busy metadata log
Key: KAFKA-13959
URL: https://issues.apache.org/jira/browse/KAFKA-13959
Project: Kafka
Issue Type: Bug
Components: kraft
Affects Versions: 3.3.0
Reporter: Jose Armando Garcia Sancio
https://issues.apache.org/jira/browse/KAFKA-13955 showed that it is possible
for the controller to not unfence a broker if the committed offset keeps
increasing.
One solution to this problem is to require the broker to only catch up to the
last committed offset when they last sent the heartbeat. For example:
# Broker sends a heartbeat with current offset of {{{}Y{}}}. The last commit
offset is {{{}X{}}}. The controller remember this last commit offset, call it
{{X'}}
# Broker sends another heartbeat with current offset of {{{}Z{}}}. Unfence the
broker if {{Z >= X}} or {{{}Z >= X'{}}}.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
