In version 2.4.0, Kafka introduced the ability for consumers to fetch data from a replica instead of a partition leader. While we already support the ability to consume data from a leader in the same AZ, leaders might move due to diverse Kafka events. KIP-392, while potentially introducing some latency, helps managing the data flow.
Describe the solution you would like
In version 2.4.0, Kafka introduced the ability for consumers to fetch data from a replica instead of a partition leader. While we already support the ability to consume data from a leader in the same AZ, leaders might move due to diverse Kafka events. KIP-392, while potentially introducing some latency, helps managing the data flow.
Supporting documentation
https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica