[
https://issues.apache.org/jira/browse/KAFKA-4225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15532153#comment-15532153
]
ASF GitHub Bot commented on KAFKA-4225:
---------------------------------------
GitHub user benstopford opened a pull request:
https://github.com/apache/kafka/pull/1932
KAFKA-4225: Replication Quotas: Control Leader & Follower Limit Separately
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/benstopford/kafka KAFKA-4225-over-KAFKA-4216
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/1932.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1932
----
commit e4fe714e8b695c08963ecd830fad60f4a47a7110
Author: Ben Stopford <benstopf...@gmail.com>
Date: 2016-09-29T08:26:05Z
KAFKA-4225: Replication Quotas: Control Leader & Follower Limit Separately
----
> Replication Quotas: Control Leader & Follower Limit Separately
> --------------------------------------------------------------
>
> Key: KAFKA-4225
> URL: https://issues.apache.org/jira/browse/KAFKA-4225
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.10.1.0
> Reporter: Ben Stopford
> Assignee: Ben Stopford
> Fix For: 0.10.1.0
>
>
> As we split the throttled replicas into Leader and Follower configs, it makes
> sense to also split the throttle limit:
> replication.quota.throttled.rate
> =>
> replication.leader.quota.throttled.rate
> &
> replication.follower.quota.throttled.rate
> So that admins have fine grain control over both sides of the replication
> process and the properties match for leader/follower applicability.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
