Jacek Żoch created KAFKA-8517:
---------------------------------
Summary: A lot of WARN messages in kafka log "Received a
PartitionLeaderEpoch assignment for an epoch < latestEpoch:
Key: KAFKA-8517
URL: https://issues.apache.org/jira/browse/KAFKA-8517
Project: Kafka
Issue Type: Bug
Components: logging
Affects Versions: 0.11.0.1
Environment: PRD
Reporter: Jacek Żoch
We have 2.0 version but it was happening in version 0.11
In kafka log there is a lot of messages
"Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This
implies messages have arrived out of order."
On 23.05 we had
Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This
implies messages have arrived out of order. New: \{epoch:181,
offset:23562380995}, Current: \{epoch:362, offset10365488611} for Partition:
__consumer_offsets-30 (kafka.server.epoch.LeaderEpochFileCache)
Currently we have
Received a PartitionLeaderEpoch assignment for an epoch < latestEpoch. This
implies messages have arrived out of order. New: \{epoch:199,
offset:24588072027}, Current: \{epoch:362, offset:10365488611} for Partition:
__consumer_offsets-30 (kafka.server.epoch.LeaderEpochFileCache)
I think kafka should either fix it "under the hood" or have information how to
fix it
There is no information, how dangerous is it and how to fix it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
