THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
Mail Thread: here
Revision History
LeaderOverThrottledRate
8th Aug 2016: Initial version
- 10th Aug 2016: Switched from a delay-based approach, which uses dedicated throttled fetcher threads, to an inclusion-based approach, which puts throttled and unthrottled replicas in the same request/response
...
- LeaderReplicationThrottledRate: The rate of throttled replication for transmitted bytes from a broker. LeaderOverThrottledRate: The difference between the throttled rate calculated by the leader, when partitions the response is formed from the log, and the rate actually sent to the follower.
- FollowerReplicationThrottledRate: The rate of throttled replication for transmitted bytes into a broker.
- PartitionBytesInRate: Equivalent to BytesInPerSec, but at a partition level (i.e. total traffic - throttled and not throttled). This is required for estimating how long a rebalance will take to complete. B/s. See usability section below.
- SumReplicaLag: This is the sum of all replica lag values on the broker. This metric is used to monitor progress of a rebalance and is particularly useful for determining if the rebalance has become stuck due to an overly harsh throttle value (as the metric will stop decreasing).
...