You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Justine Olshan (Jira)" <ji...@apache.org> on 2021/10/22 18:50:00 UTC
[jira] [Updated] (KAFKA-13394) Topic IDs should be removed from
PartitionFetchState if they are no longer sent by the controller
[ https://issues.apache.org/jira/browse/KAFKA-13394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justine Olshan updated KAFKA-13394:
-----------------------------------
Affects Version/s: 3.1.0
> Topic IDs should be removed from PartitionFetchState if they are no longer sent by the controller
> -------------------------------------------------------------------------------------------------
>
> Key: KAFKA-13394
> URL: https://issues.apache.org/jira/browse/KAFKA-13394
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.1.0
> Reporter: Justine Olshan
> Assignee: Justine Olshan
> Priority: Major
>
> With KAFKA-13102, we added topic IDs to the InitialFetchState and the PartitionFetchState in order to send fetch requests using topic IDs when ibp is 3.1.
> However, there are some cases where we could initially send topic IDs from the controller and then no longer to do so (controller changes to an IBP < 2.8). If we do not remove from the PartitionFetchState and one broker is still IBP 3.1, it will try to send a version 13 fetch request to brokers that no longer have topic IDs in the metadata cache. This could leave the cluster in a state unable to fetch from these partitions.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)