[
https://issues.apache.org/jira/browse/KAFKA-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17537501#comment-17537501
]
Igor Soarez commented on KAFKA-8366:
------------------------------------
I also ran into this issue. I managed to replicate this bug with an integration
test
[https://github.com/soarez/kafka/blob/replicate-bug-offline-partition-metrics-from-deleted-topics/core/src/test/scala/integration/kafka/api/OfflinePartitionsFromDeletedTopicTest.scala]
The problem is that the controller caches the offline partitions count, and
when it is re-elected it fails to clear it if the topic is now being deleted.
> partitions of topics being deleted show up in the offline partitions metric
> ---------------------------------------------------------------------------
>
> Key: KAFKA-8366
> URL: https://issues.apache.org/jira/browse/KAFKA-8366
> Project: Kafka
> Issue Type: Improvement
> Reporter: Radai Rosenblatt
> Priority: Major
>
> i believe this is a bug
> offline partitions is a metric that indicates an error condition - lack of
> kafka availability.
> as an artifact of how deletion is implemented the partitions for a topic
> undergoing deletion will show up as offline, which just creates
> false-positive alerts.
> if needed, maybe there should exist a separate "partitions to be deleted"
> sensor.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
