You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2015/09/28 17:34:04 UTC
[jira] [Work started] (KAFKA-2588) ReplicaManager partitionCount
metric should actually be replicaCount
[ https://issues.apache.org/jira/browse/KAFKA-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on KAFKA-2588 started by Grant Henke.
------------------------------------------
> 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.8.2.1
> Reporter: Grant Henke
> Assignee: Grant Henke
>
> 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.3.4#6332)