[
https://issues.apache.org/jira/browse/KAFKA-16986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17855758#comment-17855758
]
Justine Olshan edited comment on KAFKA-16986 at 6/17/24 11:37 PM:
------------------------------------------------------------------
Hmmm. So the earlier code block should be catching the common case of client
startup where we saw this log spam. (current epoch is null).
I guess in the upgrade case, the client is alive and you won't have current
epoch as null. This should only happen on the client during the upgrade. Once
the upgrade is complete you shouldn't see this error again. I don't know if it
makes sense to change this case since it is a legitimate resetting of the epoch
on this upgrade but I do see the argument for the log spam being annoying.
Is it sufficient that this should not be expected after the upgrade? (And let
me know if it is seen after the upgrade is fully completed.)
was (Author: jolshan):
Hmmm. So the earlier code block should be catching the common case of client
startup where we saw this log spam. (current epoch is null).
I guess in the upgrade case, the client is alive and you won't have current
epoch as null. This should only happen on the client one time during the
upgrade. Once the upgrade is complete you shouldn't see this error again. I
don't know if it makes sense to change this case since it is a legitimate
resetting of the epoch on this upgrade but I do see the argument for the log
spam being annoying.
Is it sufficient that this should not be expected after the upgrade? (And let
me know if it is seen after the upgrade is fully completed.)
> After upgrading to Kafka 3.4.1, 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, producer
> Affects Versions: 3.0.1
> Reporter: Vinicius Vieira dos Santos
> Priority: Minor
> Attachments: image.png
>
>
> 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.
> We have some applications with around 15 topics and 40 partitions which means
> around 600 log lines when metadata updates occur
> The main thing for me is to know if this could indicate a problem or if I can
> simply change the log level of the org.apache.kafka.clients.Metadata class to
> warn without worries
>
> There are other reports of the same behavior like this:
> https://stackoverflow.com/questions/74652231/apache-kafka-resetting-the-last-seen-epoch-of-partition-why
>
> *Some log occurrences over an interval of about 7 hours, each block refers to
> an instance of the application in kubernetes*
>
> !image.png!
> *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
>
> If you need any more details, please let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
