[KAFKA-7704] kafka.server.ReplicaFetechManager.MaxLag.Replica metric is reported incorrectly

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.0
• Fix Version/s: 2.2.0, 2.1.1
• Component/s: metrics
• Assignee: huxihx
• Reporter: Yu Yang
• Created: 04/Dec/18 00:35
• Updated: 06/Dec/18 13:50
• Resolved: 06/Dec/18 13:50

Description

We recently deployed kafka 2.1, and noticed a jump in kafka.server.ReplicaFetcherManager.MaxLag.Replica metric. At the same time, there is no under-replicated partitions for the cluster.

The initial analysis shows that kafka 2.1.0 does not report metric correctly for topics that have no incoming traffic right now, but had traffic earlier. For those topics, ReplicaFetcherManager will consider the maxLag be the latest offset.

For instance, we have a topic named `test_topic`:

[root@kafkabroker03002:/mnt/kafka/test_topic-0]# ls -l
total 8
-rw-rw-r-- 1 kafka kafka 10485760 Dec  4 00:13 00000000099043947579.index
-rw-rw-r-- 1 kafka kafka        0 Sep 23 03:01 00000000099043947579.log
-rw-rw-r-- 1 kafka kafka       10 Dec  4 00:13 00000000099043947579.snapshot
-rw-rw-r-- 1 kafka kafka 10485756 Dec  4 00:13 00000000099043947579.timeindex
-rw-rw-r-- 1 kafka kafka        4 Dec  4 00:13 leader-epoch-checkpoint

kafka reports ReplicaFetcherManager.MaxLag.Replica be 99043947579

Issue Links

• links to: GitHub Pull Request #5998