THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
As described above, this KIP changes the semantics of `kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions`UnderReplicatedPartitions`. Replicas which are being added as part of a reassignment will not count toward this value.
...
| Metric | Is New | Type | Includes Current Assigned Replicas | Includes Reassigning Replicas |
|---|---|---|---|---|
| kafka.server:type=ReplicaManager,name=UnderReplicatedPartitions | No | Gauge | Yes | No |
| kafka.server:type=ReplicaManager,name=ReassigningPartitions | Yes | Gauge | No | Yes |
| kafka.server:type=ReplicaManager,name=ReassignmentMaxLag | Yes | Gauge | No | Yes |
| kafka.server:type=BrokerTopicMetrics,name=ReassignmentBytesOutPerSec | Yes | Meter | No | Yes |
| kafka.server:type=BrokerTopicMetrics,name=ReassignmentBytesInPerSec | Yes | Meter | No | Yes |
Note that the `ReassignmentBytesOutPerSec` and `ReassignmentBytesInPerSec` meters are broker-level metrics. We are not proposing any topic-level metrics for tracking reassignment progress.
Compatibility, Deprecation, and Migration Plan
...