[ https://issues.apache.org/jira/browse/KAFKA-14334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jacot resolved KAFKA-14334. --------------------------------- Fix Version/s: 3.4.0 3.3.2 Reviewer: David Jacot Resolution: Fixed > DelayedFetch purgatory not completed when appending as follower > --------------------------------------------------------------- > > Key: KAFKA-14334 > URL: https://issues.apache.org/jira/browse/KAFKA-14334 > Project: Kafka > Issue Type: Bug > Reporter: Jeff Kim > Assignee: Jeff Kim > Priority: Major > Fix For: 3.4.0, 3.3.2 > > > Currently, the ReplicaManager.delayedFetchPurgatory is only completed when > appending as leader. With > [https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica] > enabled, followers will also have to complete delayed fetch requests after > successfully replicating. Otherwise, consumer fetches to closest followers > will hit fetch.max.wait.ms -- This message was sent by Atlassian Jira (v8.20.10#820010)