You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Ismael Juma (Jira)" <ji...@apache.org> on 2023/01/03 15:18:00 UTC

[jira] [Commented] (KAFKA-14255) Fetching from follower should be disallowed if fetch from follower is disabled

    [ https://issues.apache.org/jira/browse/KAFKA-14255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17654059#comment-17654059 ] 

Ismael Juma commented on KAFKA-14255:
-------------------------------------

[~dajac] A couple more projects worth filing a ticket for:
 * [https://github.com/dpkp/kafka-python]
 * [https://github.com/segmentio/kafka-go]

When it comes to librdkafka, there is an open pull request here:
 * https://github.com/confluentinc/librdkafka/pull/4122

> Fetching from follower should be disallowed if fetch from follower is disabled
> ------------------------------------------------------------------------------
>
>                 Key: KAFKA-14255
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14255
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.4.0
>            Reporter: David Jacot
>            Assignee: David Jacot
>            Priority: Critical
>
> There are clients out there that have implemented KIP-392 (Fetch From Follower) and thus use FetchRequest >= 11. However, they have not implemented KIP-320 which add the leader epoch to the FetchRequest in version 9. Without KIP-320, it is not safe to fetch from the follower. If a client does it by mistake – e.g. based on stale metadata – that could lead to offset out of range.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)