jolshan commented on PR #12378:
URL: https://github.com/apache/kafka/pull/12378#issuecomment-1190539986
Ah looks like the issue is that the oldID is null (not the new ID).
As described by this comment:
```
// If the new topic ID is valid and different from the last seen topic
ID, update the metadata.
// Between the time that a topic is deleted and re-created, the client
may lose track of the
// corresponding topicId (i.e. `oldTopicId` will be null). In this case,
when we discover the new
// topicId, we allow the corresponding leader epoch to override the last
seen value.
```
So based on this comment, we do want to override the epoch. Just curious why
this one extra log message was causing issues. I suppose one thing we can do is
check if this is the first metadata response/ if the epochs are equal, but not
sure how much this helps.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
