[ https://issues.apache.org/jira/browse/KAFKA-7093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16605361#comment-16605361 ]
Jameel Al-Aziz commented on KAFKA-7093: --------------------------------------- We've been observing the error as well. It occurred after trying to recover from a broker outage. The errors appear to prevent proper recovery or partition reassignment. > Kafka warn messages after upgrade from 0.11.0.1 to 1.1.0 > -------------------------------------------------------- > > Key: KAFKA-7093 > URL: https://issues.apache.org/jira/browse/KAFKA-7093 > Project: Kafka > Issue Type: Bug > Components: offset manager > Affects Versions: 1.1.0 > Reporter: Suleyman > Priority: Major > > I upgraded to kafka version from 0.11.0.1 to 1.1.0. After the upgrade, I'm > getting the below warn message too much. > WARN Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. > This implies messages have arrived out of order. New: \{epoch:0, > offset:793868383}, Current: \{epoch:4, offset:792201264} for Partition: > __consumer_offsets-42 (kafka.server.epoch.LeaderEpochFileCache) > How can I resolve this warn messages? And why I'm getting this warn messages? -- This message was sent by Atlassian JIRA (v7.6.3#76005)