[
https://issues.apache.org/jira/browse/KAFKA-8366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872479#comment-17872479
]
Colin McCabe commented on KAFKA-8366:
-------------------------------------
I'm sorry, but I don't think we should do this in 3.9.
The offline partitions metric is at least a decade old, and has always worked
this way in ZK mode. Changing the behavior at this point would require a KIP.
And probably even then, we'd want to create a new metric rather than changing
the behavior of the old one. Topics in "deleting" state really do represent a
lack of availability in some sense, since their names cannot be used until the
deleting state is cleared (probably manually, by starting stopped brokers.) So
some administrators may be relying on the current behavior of this metric to
detect that and realize they need to do something about it.
Deleting state doesn't exist in 4.0 / KRaft, so if you agree, we can just close
this JIRA with fix version 4.0.
> 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: Bug
> Components: controller, core, metrics
> Affects Versions: 3.1.0, 3.0.0, 3.0.1, 3.2.0, 3.1.1, 3.3.0, 3.0.2, 3.2.1
> Reporter: Radai Rosenblatt
> Assignee: Gaurav Narula
> Priority: Major
> Labels: BUG, controller, metrics, reproducible-bug
> Fix For: 3.9.0
>
>
> 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.10#820010)
