You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Sönke Liebau (Jira)" <ji...@apache.org> on 2020/04/01 12:05:00 UTC

[jira] [Resolved] (KAFKA-2225) Allow fetching from ISR

     [ https://issues.apache.org/jira/browse/KAFKA-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sönke Liebau resolved KAFKA-2225.
---------------------------------
    Fix Version/s: 2.4.0
       Resolution: Duplicate

I believe this functionality is covered by [KIP-392|https://cwiki.apache.org/confluence/display/KAFKA/KIP-392%3A+Allow+consumers+to+fetch+from+closest+replica]

> Allow fetching from ISR
> -----------------------
>
>                 Key: KAFKA-2225
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2225
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Theo Hultberg
>            Assignee: Parth Brahmbhatt
>            Priority: Major
>             Fix For: 2.4.0
>
>
> Currently clients are not allowed to fetch from replicas, even if they are in sync with the master. If I'm not missing anything significant it shouldn't be any difference fetching from the leader or an ISR, besides maybe some extra latency.
> For our use case it would be very beneficial to be able to fetch from replicas instead of just the leader. We run Kafka clusters that replicate across EC2 availability zones, and each byte sent between zones costs money. This bandwith usage costs us about the same as it costs to run the instances. If we could fetch from a replica in the same zone as the client we could avoid some of this cost.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)