[
https://issues.apache.org/jira/browse/KAFKA-13206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-13206.
----------------------------------
Fix Version/s: 3.3
Resolution: Duplicate
Thanks for the bug report.
We can finally close this because [~dajac] fixed this issue in KAFKA-13916. :)
A quick summary is that we now have an "in controlled shutdown" state for
brokers and we use it to avoid unecessary ISR churn during controlled shutdown.
The full description of the fix is in KIP-841
> shutting down broker needs to stop fetching as a follower in KRaft mode
> -----------------------------------------------------------------------
>
> Key: KAFKA-13206
> URL: https://issues.apache.org/jira/browse/KAFKA-13206
> Project: Kafka
> Issue Type: Bug
> Components: core, kraft, replication
> Affects Versions: 3.0.0
> Reporter: Jun Rao
> Assignee: HaiyuanZhao
> Priority: Major
> Labels: kip-500
> Fix For: 3.3
>
>
> In the ZK mode, the controller will send a stopReplica(with deletion flag as
> false) request to the shutting down broker so that it will stop the followers
> from fetching. In KRaft mode, we don't have a corresponding logic. This means
> unnecessary rejected fetch follower requests during controlled shutdown.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
