[jira] [Created] (KAFKA-16986) After upgrading to Kafka 3.41, the producer constantly produces logs related to topicId changes

["Vinicius Vieira dos Santos (Jira)" <ji...@apache.org>]

Vinicius Vieira dos Santos created KAFKA-16986:
--------------------------------------------------

             Summary: After upgrading to Kafka 3.41, the producer constantly produces logs related to topicId changes
                 Key: KAFKA-16986
                 URL: https://issues.apache.org/jira/browse/KAFKA-16986
             Project: Kafka
          Issue Type: Bug
          Components: clients
    Affects Versions: 3.0.1
            Reporter: Vinicius Vieira dos Santos


When updating the Kafka broker from version 2.7.0 to 3.4.1, we noticed that the applications began to log the message "{*}Resetting the last seen epoch of partition PAYMENTS-0 to 0 since the associated topicId changed from null to szRLmiAiTs8Y0nI8b3Wz1Q{*}" in a very constant, from what I understand this behavior is not expected because the topic was not deleted and recreated so it should simply use the cached data and not go through this client log line.

 

My scenario:

Application:
 * Java: 21
 * Client: 3.6.1, also tested on 3.0.1 and has the same behavior Broker: Cluster running on Kubernetes with the bitnami/kafka:3.4.1-debian-11-r52 image



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