Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Status

Current stateUnder DiscussionAccepted

Discussion thread: http://mail-archives.apache.org/mod_mbox/kafka-dev/201611.mbox/%3CCA+rPSbYk=xtcFAjBAsorgUfvXRyphvxm8+Chpa=sdzh4fShj-A@mail.gmail.com%3E here

JIRA:

Jira
showSummaryfalse
serverASF JIRA
serverId5aa69414-a9e9-3523-82ec-879b028fb15b
keyKAFKA-4458

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

Currently Kafka only reports metrics on the in-sync state of a partition, but does not give finer level detail on the number of in- / out-of- sync replicas per partition.

...

  • "kafka.cluster:type=Partition,name=InSyncReplicasCount,topic={topic},partition={partition}" – one gauge per topic partition leader
  • "kafka.cluster:type=Partition,name=ReplicasCount,topic={topic},partition={partition}" – one gauge per topic partition leader

Proposed Changes

This proposal would add the yammer gauges described above to the kafka.cluster.Partitions class, similar to the existing "UnderReplicated" metric in that class.

Performance impact should be minimal, since the new metrics rely on the same information already used to define the "UnderReplicated" metric.

Compatibility, Deprecation, and Migration Plan

 

  • The change is fully backwards compatible.
  • Users relying on custom MetricsReporter implementations would have to support the new metrics.

Rejected Alternatives

None