You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jason Gustafson (Jira)" <ji...@apache.org> on 2022/05/19 03:59:00 UTC

[jira] [Resolved] (KAFKA-13837) Return error for Fetch requests from unrecognized followers

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

Jason Gustafson resolved KAFKA-13837.
-------------------------------------
    Fix Version/s: 3.3.0
       Resolution: Fixed

> Return error for Fetch requests from unrecognized followers
> -----------------------------------------------------------
>
>                 Key: KAFKA-13837
>                 URL: https://issues.apache.org/jira/browse/KAFKA-13837
>             Project: Kafka
>          Issue Type: Bug
>            Reporter: Jason Gustafson
>            Assignee: Jason Gustafson
>            Priority: Major
>             Fix For: 3.3.0
>
>
> If the leader of a partition receives a request from a replica which is not in the current replica set, we currently return an empty fetch response with no error. I think the rationale for this is that the leader may not have received the latest `LeaderAndIsr` update which adds the replica, so we just want the follower to retry. The problem with this is that if the `LeaderAndIsr` request never arrives, then there might not be an external indication of a problem. This probably was the only reasonable option before we added the leader epoch to the `Fetch` request API. Now that we have it, it would be clearer to return an `UNKNOWN_LEADER_EPOCH` error to indicate that the (replicaId, leaderEpoch) tuple is not recognized. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)