...

replica.fetch.wait.max.ms: The changes are similar to replica.fetch.response.max.bytes

Public Interfaces

This KIP introduces two new broker level configs related to replication throttle:

follower.replication.throttled - Should all replication follower throttle

leader.replication.throttled - Should all replication leader throttle

Currently, we have two similar topic level configs:

leader.replication.throttled.replicas: A list of replicas for which log replication should be throttled on the leader side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.

follower.replication.throttled.replicas: A list of replicas for which log replication should be throttled on the follower side. The list should describe a set of replicas in the form [PartitionId]:[BrokerId],[PartitionId]:[BrokerId]:... or alternatively the wildcard '*' can be used to throttle all replicas for this topic.

However, sometimes operational people may want to throttle all the replication leader / follower. It's hard for them to achieve this using the topic level replication throttles.

Compatibility, Deprecation, and Migration Plan

• There won't be any impact on existing users.
• There won't be any change of in current behavior.
• No migration tool required

...