jolshan commented on code in PR #12078:
URL: https://github.com/apache/kafka/pull/12078#discussion_r868185826
##########
core/src/main/scala/kafka/server/DelayedFetch.scala:
##########
@@ -148,8 +148,8 @@ class DelayedFetch(delayMs: Long,
debug(s"Partition $topicIdPartition is in an offline log
directory, satisfy $fetchMetadata immediately")
return forceComplete()
case _: FencedLeaderEpochException => // Case E
- debug(s"Broker is the leader of partition $topicIdPartition, but
the requested epoch " +
- s"$fetchLeaderEpoch is fenced by the latest leader epoch,
satisfy $fetchMetadata immediately")
+ debug(s"The requested epoch $fetchLeaderEpoch of partition
$topicIdPartition" +
Review Comment:
Interesting -- I was curious since fetch from follower by definition doesn't
need the broker to be the leader (so in theory, it could still fetch despite
the leader change), though I see how the epoch is necessary to ensure the
metadata isn't stale about other aspects too? The error message just seems a
little funny given fetch from follower. :)
--
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: jira-unsubscr...@kafka.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
