Details
-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 0.8.0, 0.8.1, 0.8.1.1
-
Fix Version/s: 0.9.0.0
-
Component/s: replication
-
Labels:
Description
Currently, there is no good way to tune the replica lag configs to automatically account for high and low volume topics on the same cluster.
For the low-volume topic it will take a very long time to detect a lagging
replica, and for the high-volume topic it will have false-positives.
One approach to making this easier would be to have the configuration
be something like replica.lag.max.ms and translate this into a number
of messages dynamically based on the throughput of the partition.