THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
| Table of Contents |
|---|
This page is meant as a template for writing a KIP. To create a KIP choose Tools->Copy on this page and modify with your content and replace the heading with the next KIP number and a description of your issue. Replace anything in italics with your own description.
Status
Current state: Under Discussion
Discussion thread: here
JIRA: here
Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).
Motivation
The documentation says that ReplicationBytes(Out|In)PerSec metrics report "byte out/in (to the other brokers) rate per topic". However, according to the code, it looks like this statement is misleading , and these metrics actually report only per broker metrics. This mismatch between the documentation and actual implementation might cause problems for users who rely on these metrics. For example, as can be seen here Cruise Control relies on these metrics to build a per- topic workload model. (althoughHowever, it looks like CC authors are aware of the fact that ReplicationBytes(Out|In)PerSec do not report per topic metrics yet).
...
Alternatively, we could align documentation with the implementation and say that ReplicationBytes(Out|In)PerSec report only per broker metrics. I've actually already opened a PR for that. (I'll close the PR if this KIP is accepted)
Public Interfaces
MBean MBeans will change from current "as shown below:
| Before | After |
|---|---|
| kafka.server:type=BrokerTopicMetrics,name=ReplicationBytesInPerSec |
...
| kafka.server:type=BrokerTopicMetrics,name=ReplicationBytesInPerSec,topic=([-.\w]+) |
...
| kafka.server:type=BrokerTopicMetrics,name=ReplicationBytesOutPerSec | kafka.server:type=BrokerTopicMetrics,name=ReplicationBytesOutPerSec,topic=([-.\w]+) |
Proposed Changes
Extend the current implementation of ReplicationBytes(Out|In)PerSec to include per-topic metrics.
Compatibility, Deprecation, and Migration Plan
Since the proposed changes won't remove any existing metrics there shouldn't be any compatibility issues.
Test Plan
Newly added metrics can be tested using a JMX tool. Also, also I think it's possible to implement integration tests (I'm not sure about this but I'm ready to look into it).
Rejected Alternatives
If there are alternative ways of accomplishing the same thing, what were they? The purpose of this section is to motivate why the design is the way it is and not some other way.