[
https://issues.apache.org/jira/browse/KAFKA-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224791#comment-16224791
]
Ismael Juma commented on KAFKA-2588:
------------------------------------
A KIP would be required for this.
> ReplicaManager partitionCount metric should actually be replicaCount
> --------------------------------------------------------------------
>
> Key: KAFKA-2588
> URL: https://issues.apache.org/jira/browse/KAFKA-2588
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.10.0.0, 0.11.0.0, 1.0.0
> Reporter: Grant Henke
> Assignee: Grant Henke
> Labels: needs-kip
>
> The metrics "partitionCount" in the ReplicaManager actually represents the
> count of replicas.
> As an example if I have a cluster with 1 topic with 1 partitions and a
> replication factor of 3. The metric (aggregated) would show a value of 3.
> There is a metric called "LeaderCount" that actually represents the
> "partitionCount". In my example above the metric (aggregated) would show a
> value of 1.
> We do need to consider compatibility of consuming systems. I think the most
> simple change would be to:
> - Adjust the "partitionCount" metric to be the same value as "LeaderCount"
> - Add a "replicaCount" metric which contains the values "partitionCount" does
> today
> - Leave "LeaderCount" in for compatibility
> Documentation will need to be updated as well.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
